Received: from harrison.org (harrison.org [207.179.5.74]) by postgresql.org (8.11.3/8.11.1) with SMTP id f3RIj8345250 for ; Fri, 27 Apr 2001 14:45:08 -0400 (EDT) (envelope-from jlarson@harrison.org) Received: (qmail 23148 invoked from network); 27 Apr 2001 12:45:06 -0600 Received: from dhcp-208-187-123-53.avalanchenet.net (HELO CANDLEFIRE) (208.187.123.53) by harrison.org with SMTP; 27 Apr 2001 12:45:06 -0600 Date: Fri, 27 Apr 2001 12:45:18 -0600 From: Jason k Larson X-Mailer: The Bat! (v1.51) Reply-To: Jason k Larson X-Priority: 3 (Normal) Message-ID: <14461714625.20010427124518@harrison.org> To: PgSQL-PHP Subject: RE: HTTP authentication MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200104/42 X-Sequence-Number: 295 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. If you are interested I could send you my library .. it's pretty basic. Jason k Larson Web Developer++ CM> I guess simple HTTP authentication where I get the username and pass and CM> check it with the database... Maybe encrypting. CM> What would you recommend? I haven't done something like that before. CM> It's my first project which needs authentication! CM> Don't have a clue:)