RE: [PHP-DB] authorization idea (good or bad?)
| From: | John Guynn | Date: | Wed, 04 Oct 2000 17:34:52 +0000 |
| Subject: | RE: [PHP-DB] authorization idea (good or bad?) | ||
| Groups: | php.db | ||
| Request: | Send a blank email to php-db+get-3320@lists.php.net to get a copy of this message | ||
That's not my intention but in my case it should (notice I said should)
never happen.
Also to anyone following this thread, keep in mind that I will be entering
the IP addresses, not letting anyone enter them or having automated
entry...anyone who has an address that does not match will be forced to use
username/password.
At any rate, I've seen enough arguments against this idea to settle on
username and password only...and I am only going to compare the md5 hash of
the username and password, not cleartext.
-----Original Message-----
From: Martin Neimeier [mailto:nei@ibn.de]
Sent: Wednesday, October 04, 2000 12:21 PM
To: John Guynn
Cc: Php-Db (E-mail)
Subject: Re: [PHP-DB] authorization idea (good or bad?)
John Guynn wrote:
>
> I'm trying to decide if this is a good idea or not. If I have a table
with
> usernames, passwords, and IP addresses I can look at the user's ip address
> with $REMOTE_ADDR, see if that matches what's in the database and allow
> access to the page and interact with the database (the page I'm wanting to
> protect is the page that I use to edit the contents of tables) but if the
IP
> address does not match any records ask for a username and password,
recheck
> with the "security" table and allow access if it matches an entry.
>
> Of course this is assuming I know the IP address(es) of the computer(s)
that
> would be accessing this database most often.
>
> Good idea or bad idea?
>
> John Guynn
>
> --
> PHP Database Mailing List (http://www.php.net/)
> To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net
> For additional commands, e-mail: php-db-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
Hello,
here is another problem: IP-Masquerading
If more than one client from behind a masq'd network connects to your site,
they have all the same
ip and
are allowed to access your site. Is this your intention ? I think not.
cu
Martin