Received: from viemta05.chello.at (viemta05.chello.at [195.34.133.55]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2DMMLx01921 for ; Tue, 13 Mar 2001 17:22:21 -0500 (EST) (envelope-from cm@chello.at) Received: from server ([212.17.110.55]) by viemta05.chello.at (InterMail vK.4.03.02.00 201-232-124 license 9caa03a7df1d31c048ffcc0d31ac5855) with SMTP id <20010313222215.KUZU18647.viemta05@server> for ; Tue, 13 Mar 2001 23:22:15 +0100 From: "Christian Marschalek" To: "PostgreSQL [PHP]" Subject: RE: Re: Re: Secure pages Date: Tue, 13 Mar 2001 23:23:10 +0100 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal In-Reply-To: X-Archive-Number: 200103/14 X-Sequence-Number: 198 Why not ask for a password, encrypt it (with 128bit or something;), check it with the database (which has the encyrpted pwds) and pass the encrypted password from page to page... like: or just a variable which is one indicating that the password was typed in correctly at least once! For the mater of direct accessing you could just check if the pwd (or the var) was passed (is one) and if not -> well no access... You could also use a cookie and check for it (with the encrypted pwd) but (I don't know why) cookies seem preaty unsafe too me :o) just my two cents;)