IntegraMOD

We have discussed a lot about CrackerTracker on this forum last months.

Like many persons, I run in so much trouble with CrackerTracker that I finally just managed to "turn it off". Sure for the security, this is the best, but it seemed too long to debug everything by myself...

Tu remove CrackerTracker, I found two different ways. I will just repost them here, hoping that newcomers complaining about this MOD will find a way to get rid of it - at their own risks, of course...

1/ The fast way (source : [url=http]here[/url] - by Ma ®ÃƒÆ’‚ ©uS)

In common.php - find:

Code: Select all

// CrackerTracker v5.xinclude($phpbb_root_path . 'ctracker/engines/ct_security.' . $phpEx);

And comment the second line. This will solve all problems immediately - lowering the safety of your board, though...


2/ The second option (source ]here[/url] - by ZacFields)

Code: Select all

Step 1: Open up /ctracker/engines/ct_security.php-----------------------------------------------------------Step 2: FIND:  define('CT_DEBUG_MODE', false);  And replace the "false" to "true" (without quotations)-----------------------------------------------------------Step 3: Now go through your admin panel and do ALL of the things that have been causing you to receive the error message. Go through your config, go through your PCP wizard, go through your forum management, and make as many of those error messages pop up as you can find.-----------------------------------------------------------Step 4: Now go to ACP => CrackerTracker => Log Manager.  Then once you're in the log manager, click on "VIEW" next to where it says "Debug Entries"-----------------------------------------------------------Step 5: Open up notepad, and copy/paste all the files it tells you to open. For instance, tell you to open "/admin/admin_board.php" and it will give you instructions on what to do with it... ignore the instructions, but just go through the page and Copy/Paste all the files that it is telling you to open into a notepad or word document.  *Again, for the purpose of disabling CrackerTracker, ignore the rest of the instructions, just copy down the files*-----------------------------------------------------------Step 6: Now, for EACH of those files, you will need to open it up and find this code (should be near the top)  define('IN_PHPBB', true);  UNDERNEATH this code, you will add this code:  define('CT_SECLEVEL', 'LOW');-----------------------------------------------------------*NOTE* In some files, underneath this code:  define('IN_PHPBB', true);  You might find this code:  define('CT_SECLEVEL', 'MEDIUM');  In this case, you will just need to change the "Medium" to "Low."----------------------------------------------------------Then remember to go back to step 1 of this, and change the "TRUE" back to "FALSE" in the /ctracker/engines/ct_security.php file.    There you have it. Do this to all the files that are giving you the cracker-tracker error and it should unlock automatically for you.  In fact, for most of you, here are most of the files you will need to do this to:  /admin/admin_board.php/profile.php/admin/admin_pcp_wizard.php

I tried both methods, they seem to work. I currently use the first one.


My question is the following: tens of corrections have been posted to kill the False Positives alarms. Is a global patch going to be released soon? If we apply this patch on our forums, what are the chances that we won't get any unexpected errors?


I think getting more information on such patch will make many persons more confident using 1.4.1... Which is really far superior to the previous version.


sanji

Actually I haven't had alot of problems with CT
Maybe 12-15 debugs at the most.

Did the debug, retry and if still get CT message, set to LOW and never had anymore problems.

More of a pain in the ass at first because my site was new and all the CT errors came all at once.
But once I started debuggging, No more CT problems.

I have had 1 in the last month because I was trying a new feature in the forum I hadn't tried before.
Most came up in the first 1-2 months, but filtered them all out.

I understand that the issue is manageable. Still, errors coming out for 1-2 months might be disturbing enough for new members to leave, and this is especially an issue for small boards.
That's why I disabled this MOD, as I tought the risk of loosing members was much higher that being attacked.

Still, if a patch is provided, I probably would give it a try.

sanji