Re: session.save_path is a big security hole!
| From: | Raditha Dissanayake | Date: | Fri, 05 Sep 2003 01:07:14 +0000 |
| Subject: | Re: session.save_path is a big security hole! | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-161710@lists.php.net to get a copy of this message | ||
Mmmmm, very interesting thread, thanx for starting this. Good comments curt.
It's because of the 'suspect' nature of sessions and cookies that i never place userid,username or password in sessions. My tactic is to aways have 2 column mysql table and store session identifier and corresponding userid in it. So even if someone does create a bogus session they still have to find a way to insert a userid into the mysql db.1. (!!!) Absolutely easily generate new sessions with any content for every site on server.
3. Flood every http server writable directory with thousands or millions files. set quotas. Some admins even set quota for the root user, which is inconvinient by safe.
-- http://www.raditha.com/php/progress.php A progress bar for PHP file uploads.