Posted by: Anonymous
[ip: 89.220.107.198]
on July 23, 2008 07:11 PM
Danger Will Robinson!
Watch out with the cp php -> .php.bkp example; if you do this in a place where your web-server (with php-module enabled) can access it you could have a code leak! (.php will be interpreted and .bkp will serve the plain text contents of the file!)
A possible example; http://server/config.php.bkp would disclose sensitive data (a lot of php applications store their database credentials here, among other things...)
Also look out when using editors with a backup function; for example the joe editor leaves its backup files with a trailing ~, backup of config.php will be config.php~ causing the same effect.
Learn about Linux
Download Linux
Get Linux help
CLI Magic: For geek cred, try these one-liners
Posted by: Anonymous [ip: 89.220.107.198] on July 23, 2008 07:11 PMWatch out with the cp php -> .php.bkp example; if you do this in a place where your web-server (with php-module enabled) can access it you could have a code leak! (.php will be interpreted and .bkp will serve the plain text contents of the file!)
A possible example; http://server/config.php.bkp would disclose sensitive data (a lot of php applications store their database credentials here, among other things...)
Also look out when using editors with a backup function; for example the joe editor leaves its backup files with a trailing ~, backup of config.php will be config.php~ causing the same effect.
-----
news at eleven
#