You should be fixing the code that causes the problem, rather than throw stuff at it and hope it blocks the malicious stuff. Your .htaccess blocks access to /proc, which is good, but it's not the only thing you want to protect. Blacklisting like this won't get you far, as there are dozens of othe...
First of all thank you for your generous and long answer. It is now a bit more clear that my code needed to be sort out. However it is a huge job for me and I am not sure if I have a money to ask anybody. However I try to do my best step by step. Hope I will still fast enough before someone will find me again.
My issue is I don't know where the attack came from and which bit should I fix first. php.ini: I've got register_globals and magic_quotes off for a start
the site really don't need any file/folder writing as I don't have upload and writing function. I only work in the DB. This would assume that I could change the /public_html/ folder to 711 so I can do everything and others can execute files. Am I correct? thanks
@ Hendrik Brummermann yes you are right, however I need to find the root and I am not that clever yet. So I am searching the solution meanwhile I try to cover the obvious holes so I can work on the code then, but I don't know how to find the hole in my code yet. Therefore appologise for the same question but php.ini and .htaccess would be the easiest and fastest Temporary solution I believe
Discussion between tdammers and Andra…
Discussion between tdammers and Andra…