From: Timothy_Maguire@hartehanks.com
To: David Olbersen <dave@slickness.org>
Cc: Michael Fork <mfork@toledolink.com>
Cc: Timothy_Maguire@hartehanks.com
Cc: Paul Joseph McGee <mcgee@student.cs.ucc.ie>
Cc: pgsql-php@postgresql.org
Subject: Re: Re: Secure pages
Date: Tue, 13 Mar 2001 15:48:29 -0500
Message-ID: <OF3CE0DA25.509B61DE-ON85256A0E.0071EAA3@hartehanks.com> (raw)
what i have sone in the past for passwords on web pages is have something
like:
<?
if(md5($MyCookie) != "anencryptedpassword") {
header("Location:http//homepage.com/whatever");
}
that way even if someone got the file and wanted to find out what the "some
value" was it would be encrypted.
There are probably still ways around this, but for the info you are hiding
from people, this is probably safe enough, at least for me it is.
David Olbersen <dave@slickness.org>@postgresql.org on 03/13/2001 02:50:45
PM
Sent by: pgsql-php-owner@postgresql.org
To: Michael Fork <mfork@toledolink.com>
cc: <Timothy_Maguire@hartehanks.com>, Paul Joseph McGee
<mcgee@student.cs.ucc.ie>, <pgsql-php@postgresql.org>
Subject: Re: Re: Secure pages
On Tue, 13 Mar 2001, Michael Fork wrote:
->not if the include file ends with a .php -- since it is in <? ?>, anybody
->acessing the file from a web browser would not be able to see it.
I misunderstood, I thought you meant that you would put that code in an
included
file. Which anybody could get at. However the code being hidden doesn't
change
that I could look for a cookie from your domain, see it's value, and still
create another cookie.
What you're all looking for is a *session based* authentication system. PHP
does
this, and you can do it yourself if you have a database set up.
-- Dave
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-php@postgresql.org
Cc: Timothy_Maguire@hartehanks.com, dave@slickness.org, mfork@toledolink.com, mcgee@student.cs.ucc.ie
Subject: Re: Secure pages
In-Reply-To: <OF3CE0DA25.509B61DE-ON85256A0E.0071EAA3@hartehanks.com>
References: <OF3CE0DA25.509B61DE-ON85256A0E.0071EAA3@hartehanks.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox