Blog Spam Update #2

Got a chance to look at the backend code for the MT-Scode Captcha plugin and figured out there was a conflict with MT-Blacklist. Once I modified MTBLPost.pm (by adding the same security check at line 75 that was added to comments.pm), the security check started working!
Woo-hoo! Take that, ass-clown spammers!
With this new security measure in place, I will soon work on re-opening all the old posts…
[UPDATE: All old posts have been re-opened for comments.]
Related posts:
Filed under: Meta
Like this post? Subscribe to my RSS feed and get loads more!







Here’s an interesting item for you, the king o’ spam, John.
The security code is 2 digits the first time you try to enter a comment. If you enter it incorrectly, or not at all, the resulting comment re-entry page uses a 6 digit security code.
Get cracking!
Not sure what that’s about. It was set to 2 digits – then I bumped it up to six and rebuilt. Maybe it’s a browser caching issue?
Damn. Got spammed today. Back to the drawing board.
Do you have a log of who spammed you and how (at the HTTP level)? That might help us figure out a way to stop it.
We can get an IP address, but they are forged.
No I mean the actuall HTTP Post itself – it might help to see the form fields.
Not that I am aware of. JP?
I don’t think we have logs of that.