ive gotten into peoples servers by renaming a shell scripts extension to some **** like file.nth/.sisx/.rb/.pl/.asp etc etc as long as the webservers mime-types recognizes these extensions as executables it will process the file as a php script no matter what
best protection is having a secure apache.conf/httpd.conf file before implementing any htaccess **** and what not
one way to do that is use mod_security and block the arrays scripts like c99shell and r57 shell use and next method is a simple program called bastille which secures the server be-it in a beginners way
my site is exploitable but if anyone gets access via a shell script they cant do **** all as i have my hard drives on my server read only so no downloading, my dirs where my scripts are set to root user access only so the nobody/www-data users cant access my files and i use 15 digit alphanumeric passwords so brute force safe
over the years running lavalair i have learnt so many lessons and this is the reason why my latest script hasn't been released by anyone
anyhow in a nutshell server protection should be sorted from the basics, i.e apache/mysql config files and not solely relying on php workarounds
best protection is having a secure apache.conf/httpd.conf file before implementing any htaccess **** and what not
one way to do that is use mod_security and block the arrays scripts like c99shell and r57 shell use and next method is a simple program called bastille which secures the server be-it in a beginners way
my site is exploitable but if anyone gets access via a shell script they cant do **** all as i have my hard drives on my server read only so no downloading, my dirs where my scripts are set to root user access only so the nobody/www-data users cant access my files and i use 15 digit alphanumeric passwords so brute force safe
over the years running lavalair i have learnt so many lessons and this is the reason why my latest script hasn't been released by anyone
anyhow in a nutshell server protection should be sorted from the basics, i.e apache/mysql config files and not solely relying on php workarounds
Comment