freebsd-nq/crypto
Dag-Erling Smørgrav 2adf4e49c2 Linux-PAM's pam_start(3) fails with a bogus error message if passed the
pam_conv argument is NULL.  OpenPAM doesn't care, but to make things
easier for people porting this code to other systems (or -STABLE), use
a dummy struct pam_conv instead of NULL.

Pointed out by:	Damien Miller <djm@mindrot.org>
2003-02-03 14:10:28 +00:00
..
heimdal This commit was generated by cvs2svn to compensate for changes in r109641, 2003-01-21 14:19:06 +00:00
kerberosIV Background: 2003-01-29 18:14:29 +00:00
openssh Linux-PAM's pam_start(3) fails with a bogus error message if passed the 2003-02-03 14:10:28 +00:00
openssl Background: 2003-01-29 18:14:29 +00:00
telnet Background: 2003-01-29 18:14:29 +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.