freebsd-src/crypto
Dag-Erling Smørgrav 96e215ad81
Some checks are pending
Cross-build Kernel / amd64 ubuntu-22.04 (clang-15) (push) Waiting to run
Cross-build Kernel / aarch64 ubuntu-22.04 (clang-15) (push) Waiting to run
Cross-build Kernel / amd64 ubuntu-24.04 (clang-18) (push) Waiting to run
Cross-build Kernel / aarch64 ubuntu-24.04 (clang-18) (push) Waiting to run
Cross-build Kernel / amd64 macos-latest (clang-18) (push) Waiting to run
Cross-build Kernel / aarch64 macos-latest (clang-18) (push) Waiting to run
Revert "openssh: Don't try to bind to unsupported addresses"
This doesn't actually do anything useful, since getifaddrs() will only
return supported addresses.  The root cause of the issue described in
the PR lies earlier in the connection timeline, around the start of the
ssh_create_socket() function.

This reverts commit e5ff8e7977.

PR:		195231
2025-11-04 21:13:11 +01:00
..
heimdal kadmin.8: Document the new dump -f flag 2025-10-05 14:06:26 -07:00
krb5 mit-krb5.pc: Add missing -lkrb5profile 2025-10-11 10:20:44 +00:00
libecc Add 'crypto/libecc/' from commit '736d663976d1768533badbf06581481d01fade4c' 2025-01-01 15:11:18 -06:00
openssh Revert "openssh: Don't try to bind to unsupported addresses" 2025-11-04 21:13:11 +01:00
openssl OpenSSL: install .pc files from the exporters subdir 2025-10-16 23:42:13 -07:00
.gitignore crypto/openssl: remove autogenerated files 2025-10-16 23:38:33 -07:00
README Two more $FreeBSD$ stragglers 2023-08-25 15:14:19 -06:00

This directory is for the EXACT same use as src/contrib, except it
holds crypto sources.  In other words, this holds raw sources obtained
from various third party vendors, with FreeBSD patches applied.  No
compilation is done from this directory, it is all done from the
src/secure directory.  The separation between src/contrib and src/crypto
is the result of an old USA law, which made these sources export
controlled, so they had to be kept separate.