Received: from harrison.org (harrison.org [207.179.5.75] (may be forged)) by postgresql.org (8.11.3/8.11.1) with SMTP id f3RIk2345784 for ; Fri, 27 Apr 2001 14:46:02 -0400 (EDT) (envelope-from jlarson@harrison.org) Received: (qmail 23633 invoked from network); 27 Apr 2001 12:46:00 -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:46:00 -0600 Date: Fri, 27 Apr 2001 12:46:13 -0600 From: Jason k Larson X-Mailer: The Bat! (v1.51) Reply-To: Jason k Larson X-Priority: 3 (Normal) Message-ID: <2961768953.20010427124613@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/41 X-Sequence-Number: 294 This is all good but needs to be dealing with the password as a hash/digest not the real clear text password. I would use SHA1 (SHA-160) or MD5. Jason k Larson Web Developer++ AL> The way i do it is have a separate table in the database that keeps track of AL> users and passwords for the application. AL> I use the WWW-Authenticate header to get $PHP_AUTH_USER and $PHP_AUTH_PW AL> I run them through the table using a select query. If I come back with a AL> match, I set a variable, $auth, equal to true. AL> If $auth is equal to true, they can perform whatever functions in the page I AL> have. AL> I don't have a log out button, but all I would probably do would be set AL> $auth = false and unset the $PHP... variables. AL> Adam Lang AL> Systems Engineer AL> Rutgers Casualty Insurance Company AL> http://www.rutgersinsurance.com AL> ----- Original Message ----- AL> From: "Christian Marschalek" AL> To: "'Adam Lang'" AL> Cc: "[PHP] PostgreSQL" AL> Sent: Friday, April 27, 2001 11:43 AM AL> Subject: RE: [PHP] HTTP authentication