From owner-freebsd-hackers Thu Jun 26 09:44:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA29624 for hackers-outgoing; Thu, 26 Jun 1997 09:44:23 -0700 (PDT) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA29619 for ; Thu, 26 Jun 1997 09:44:20 -0700 (PDT) Received: from localhost (brandon@localhost) by ice.cold.org (8.8.5/8.8.5) with SMTP id KAA09637 for ; Thu, 26 Jun 1997 10:44:28 -0600 (MDT) Date: Thu, 26 Jun 1997 10:44:28 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: crypt() inconsistancies Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk 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