Re: [PHP] session.save_path is a big security hole!

2003-09-05 Thread Raditha Dissanayake
Unfortunetly setting quotes (eg for apache user)doesnt prevent from flooding out entire disk. For example i can have running a script that will check user directories every 15 minutes and if some directory will contain large amount of apache generated files, user account will be disabled and

Re: [PHP] session.save_path is a big security hole!

2003-09-04 Thread Rx
"Raditha Dissanayake" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > M, very interesting thread, thanx for starting this. Good comments curt. > > > >>1. (!!!) Absolutely easily generate new sessions with any content for every > >>site on server. > >> > >> > > > > > > > > It's be

Re: [PHP] session.save_path is a big security hole!

2003-09-04 Thread Raditha Dissanayake
M, very interesting thread, thanx for starting this. Good comments curt. 1. (!!!) Absolutely easily generate new sessions with any content for every site on server. It's because of the 'suspect' nature of sessions and cookies that i never place userid,username or password in sessions

Re: [PHP] session.save_path is a big security hole!

2003-09-04 Thread Curt Zirzow
* Thus wrote John W. Holmes ([EMAIL PROTECTED]): > >>You didnt understand. I change save.session_path to other's site session > >>directory, do session_start(), write every variable what i want, write > >>down > >>session number, go to this site and using this generated session. You > >>cannt > >

Re: [PHP] session.save_path is a big security hole!

2003-09-04 Thread John W. Holmes
You didnt understand. I change save.session_path to other's site session directory, do session_start(), write every variable what i want, write down session number, go to this site and using this generated session. You cannt prevent this ever! Does enabling safe_mode counter any of these writing

Re: [PHP] session.save_path is a big security hole!

2003-09-04 Thread Curt Zirzow
* Thus wrote Rx ([EMAIL PROTECTED]): > > "Curt Zirzow" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > * Thus wrote Rx ([EMAIL PROTECTED]): > > > > You can set the value with > > php_admin_value save_path "/tmp" > > If i set php_admin_value, user STILL can change the value with

Re: [PHP] session.save_path is a big security hole!

2003-09-04 Thread Rx
"Curt Zirzow" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > * Thus wrote Rx ([EMAIL PROTECTED]): > > Theres absolutely no control over session.save_path parameter in php. By > > setting it to every directory he wants, every user can: > > You can set the value with > php_admin_value

Re: [PHP] session.save_path is a big security hole!

2003-09-04 Thread Curt Zirzow
* Thus wrote Rx ([EMAIL PROTECTED]): > Theres absolutely no control over session.save_path parameter in php. By > setting it to every directory he wants, every user can: You can set the value with php_admin_value save_path "/tmp" > > 1. (!!!) Absolutely easily generate new sessions with any cont

[PHP] session.save_path is a big security hole!

2003-09-04 Thread Rx
Theres absolutely no control over session.save_path parameter in php. By setting it to every directory he wants, every user can: 1. (!!!) Absolutely easily generate new sessions with any content for every site on server. 2. Delete other users sessions by setting gc to 100 and probably legal files