4.2.1 PL1 hacked, what to look for in logs

[Mark.B]

There's nothing in 4.2.2 that would break a modification that worked on 4.2.1.

Upgrade to 4.2.2 and add the following line to your /includes/config.php file, right under the <?php line:

PHP Code:

define('SKIP_ALL_ERRORS', true); 


[ifitsmedia]

For everyone who is saying to upgrade as a response to this thread, are you suggesting that vBulletin 4.2.1 PL1 is not secure? I don't think that is the case.

[ForceHSS]

It is secure, it just 4.2.2 is just more secure, but if you like what you have stay with it as long as you have installed the latest security patch that came out a few months ago.

[Disco_Stu]

How is it that hackers can find the security holes so easily before they are spotted by vBulletin developers? Are they smarter than the software developers at vBulletin or is vBulletin not spending enough time and effort on QC ?

It seems like they release a new version and wait for the hackers to show them where they messed up instead of conducting enough testing prior to the release.

[Paul M]

Originally Posted by Mark.B

There's nothing in 4.2.2 that would break a modification that worked on 4.2.1.

Upgrade to 4.2.2 and add the following line to your /includes/config.php file, right under the <?php line:

PHP Code:

define('SKIP_ALL_ERRORS', true); 


Unless there is a very good reason to disable all error reporting, please use SKIP_DS_ERRORS.

That reverts 4.2.2 to use the same as 4.2.1 (and previous versions).