Hi guys,
as per my last post I keep having my php files edited with 64bit encrypted cack that redirects my customers and staff to dodgy sites.
I know it is something to do with my setup and my knowledge is limited..... so - if I password protect the public html file that my sugar is saved on - that should then give me a control to show that it has nothing to do with sugar itself???
Can anyone see a weakness in my logic? If it is password protected to get to Sugar let alone the Sugar passwords themselves then in theory they should not be able to get to the php files to edit them?
I would be grateful of your thoughts?
Ta
Syfa


LinkBack URL
About LinkBacks



Reply With Quote
Bookmarks