R: [PHP-DB] authorization idea (good or bad?)

If this were for an Intranet, it may be good, but: 1. do you mean store passwords as plain text? 2. it'll run only when desktop pc's use fixed IP addresses, not given through DHCP. Addresses too may change faster than you think. For Internet: forget it! Security and trust seem not to be allowed here. But overall: who is the target? Ciao Roberto > -----Messaggio originale----- > Da: John Guynn [mailto:John.Guynn@telescan.com] > Inviato: mercoledì 4 ottobre 2000 15.11 > A: Php-Db (E-mail) > Oggetto: [PHP-DB] authorization idea (good or bad?) > > > 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 >