Date: Thu, 26 Jun 1997 10:44:28 -0600 (MDT) From: Brandon Gillespie <brandon@roguetrader.com> To: freebsd-hackers@freebsd.org Subject: crypt() inconsistancies Message-ID: <Pine.BSF.3.96.970626104212.9631A-100000@ice.cold.org>
next in thread | raw e-mail | index | archive | help
Just a note as I'm re-reviewing the changes I have for crypt()... In the
docs it says:
The function crypt() returns a pointer to the encrypted value on
success and NULL on failure.
At first I was pretty happy about this, as having a means of specifying an
error would be wonderful. However, double checking in Digital Unix and
Unixware shows that this returning NULL behaviour is not a standard
behaviour.
Is there a specification (POSIX?) for how crypt() should behave, and if
so, could somebody forward it to me so I can make sure the newer code
follows it (this code includes SHA-1 encryption, and will allow $MD5$.. or
$SHA1$ etc tags, as well as numbers)
-Brandon Gillespie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970626104212.9631A-100000>