Received: from viemta06.chello.at (viemta06.chello.at [195.34.133.56]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3RKtb364190 for ; Fri, 27 Apr 2001 16:55:37 -0400 (EDT) (envelope-from cm@chello.at) Received: from server ([212.17.110.55]) by viemta06.chello.at (InterMail vK.4.03.02.00 201-232-124 license 6aea1bd1f01aef5a9a73363c16ebee43) with ESMTP id <20010427205534.SFMO27182.viemta06@server>; Fri, 27 Apr 2001 22:55:34 +0200 From: "Christian Marschalek" To: "'Jason k Larson'" Cc: "[PHP] PostgreSQL" Subject: RE: Re[2]: HTTP authentication Date: Fri, 27 Apr 2001 22:56:40 +0200 Message-ID: <000301c0cf5c$8ed8fd20$0200a8c0@server> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: <4061045093.20010427123409@harrison.org> X-Archive-Number: 200104/44 X-Sequence-Number: 297 > From: Jason k Larson [mailto:jlarson@harrison.org] > > I have written a library to handle this. It is fairly secure > not allowing the password to be seen except as an MD5 digest. > The only requirement is being able to deal with the MD5 > digest. For instance I have a PgSQL Table with fields User > ID, Username, Password, and Status. I give each User and > unique ID and the Password field contains and MD5 digest of > the password and I use status (boolean) to tell me if the > user is active or not. What exactly is a MD5 diggest? :o)