Tag Info

New answers tagged


I basically agree with Simon Hayters statement that if they gained shell access - unless they had limited shell access by injection into say a php application that was using shell_exec - I personally would start thinking about restoring the system from trusted sources. But then the question becomes - if you don't learn how they got in that time - how can ...


If they are able to login via your SHELL then its pretty much game over and as mentioned by @w3d Apache log files are least of your worries. Apache writes to log files directly, no one can view those logs unless they are stored within the hosting path. If security is a major concern then you should confirm that you use the following practices: Your ...


You could just include a rule in your index.php to check the current time against the time you want to launch. So if you wanted to launch on 2015-12-01 at 15:00UTC, something like this should work: <?php if(time() < '1448982000'){ header("Location: https://www.example.com/",TRUE,301); exit; }?> Drop that into the very top of index.php and ...


It's really risky solution. Some browser (or ISPs) can cache index.html. After refreshing page, some users can find some troubles there. I believe much better solution will be using only one .php file as a routing file, which will detect time and do different things on these time frames.


My apache installation has a php5.conf file I added this to it. <FilesMatch ".+\.html$"> SetHandler application/x-httpd-php </FilesMatch> In my .htaccess file I also changed AddType application/x-httpd-php5 .html to AddType application/x-httpd-php .html Scott


<!--?php echo "It works!"; ?--> This is what you see when you analyse the element using the browsers Object Inspector ie. the interpreted source. This is not the HTML source as sent from the server (ie. "view source"). Basically, your HTML pages are not being processed by PHP. You probably need to check with your host as to the correct directive ...


In you case it is already securised as setup.php is not allowed. More advices: keep your phpmyadmin uptodate change default folder name Here you can find an extra rule for Apache to redirect to nowhere 90% of bots: RewriteCond %{HTTP_USER_AGENT} ^-?$|curl|perl|python [NC,OR] RewriteCond %{REQUEST_METHOD} !^(GET|HEAD|POST)$ [OR] RewriteCond ...

Top 50 recent answers are included