Code: Select all
<!-- link rel="stylesheet" href="templates/subSilver/{T_HEAD_STYLESHEET}" type="text/css" -->
Code: Select all
<link rel="stylesheet" href="templates/subSilver/{T_HEAD_STYLESHEET}" type="text/css">
Code: Select all
<style type="text/css">
<!--
/*
Code: Select all
/* Import the fancy styles for IE only (NS4.x doesn't use the @import function) */
@import url("templates/subSilver/formIE.css");
-->
</style>
ByteEnable wrote: Also to help out, you will want to modify viewtopic.php to drop those the santy, anti-santy and the occasional cracker from trying to exploit security holes in older versions of phpBB. Each attempt causes bandwidth on your server. I have hundreds of attempts daily.If your forum is using phpBB, you can add the following code to your viewtopic.php to stop the crack attempts all together (which also reduces server load):
$phpBBCrack = strpos(strtoupper($HTTP_GET_VARS['highlight']), "SYSTEM");
if ( $phpBBCrack !== false ) { die; }
You want to add the above code around line 485, just above the "// Split words and phrases" comment. The above code will render a blank page on crack attempts. However, this code should not be used as a substitute for an upgrade to phpBB 2.0.11, although it is compatible.
From: "phpBB.com Took Down by Crackers"
makc wrote: I sort of couldn't believe it, so I made some calculations...
Thu Nov 07, 2002 2:46 am, that is 478 days ago.
SamG wrote: I think Van Zant's question was targeting the advisability of using in 2.0.17 the patch that addressed modifying "viewtopic.php to drop those the santy, anti-santy and the occasional cracker from trying to exploit security holes in older versions of phpBB. Each attempt causes bandwidth on your server."
True, which is why there is the vastly superior .htaccess method. Bounce 'em hard by using RewriteRule to send them right back to 127.0.0.1