freebsd-skq/crypto
Hajimu UMEMOTO 7ac3260308 sshd didn't handle actual size of struct sockaddr correctly,
and did copy it as long as just size of struct sockaddr.  So,
If connection is via IPv6, sshd didn't log hostname into utmp
correctly.
This problem occured only under FreeBSD because of our hack.
However, this is potential problem of OpenSSH-portable, and
they agreed to fix this.
Though, there is no fixed version of OpenSSH-portable available
yet, since this problem is serious for IPv6 users, I commit the
fix.

Reported by:	many people
Reviewed by:	current@ and stable@ (no objection)
MFC after:	3 days
2002-09-09 16:49:11 +00:00
..
heimdal Pass the pointy hat! Remove accidently imported files. 2002-08-30 21:53:25 +00:00
kerberosIV Resurrect as an empty file to unbreak the build. We have everything we 2002-05-08 17:19:02 +00:00
openssh sshd didn't handle actual size of struct sockaddr correctly, 2002-09-09 16:49:11 +00:00
openssl Resolve conflicts. 2002-08-10 01:50:50 +00:00
telnet Encrypted strings (after hex decoding) aren't null terminated, because 2002-08-22 06:19:07 +00:00
README Note that crypto/ is not used to build in, people should see secure/ 2001-02-10 04:47:47 +00:00

$FreeBSD$

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.