Date: Wed, 24 Sep 1997 23:58:37 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: brandon@roguetrader.com (Brandon Gillespie) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: crypt() returning an error... Message-ID: <199709242358.QAA29468@usr03.primenet.com> In-Reply-To: <Pine.BSF.3.96.970924115746.6054B-100000@roguetrader.com> from "Brandon Gillespie" at Sep 24, 97 12:06:29 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> The man page on crypt() states that a NULL will be returned instead of a > pointer to a string, if an error occurred. The MD5 crypt does not follow > this, however DES crypt does. Furthermore, in the attempt to hunt out a > 'standard' for handling error codes, I have checked how other crypt() > implementations function. OpenBSD for some unknown reason returns the > string: > > ":" > > Where Digital Unix also returns a NULL, as does Unixware--however their > manual pages do not specify NULL as a valid return value. Forget that; we want to know how you are making a straight MD5 hash cause an error in the first place... 8-) 8-). > crypt("", "") > > With MD5 will actually return an encrypted value, with a zero-length salt. > After my changes, this will return a NULL instead. > > Anybody forsee any problems with this? I do not, but I figured I would > bring it up... You should wrapper this; I don't know if "crypt" is enough of a wrapper. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709242358.QAA29468>