Revenge of AntiBot Before continuing, please make sure you are familiar with the first segment on AntiSearch.
Antionline/AntiSearch "your portal into the world of hackers and information security"? 07.03.99 We have a few more issues to bring up with AntiBot/AntiSpider/AntiSearch/AntiWhatever. =-= [Is there any question of AntiSearch NOT archiving Attrition not being a personal issue? This shows Vranesevich know and approved of his program hitting our site.] From: John Vranesevich (JP@AntiOnline.com) To: firstname.lastname@example.org Date: Sun, 28 Feb 1999 18:01:07 -0500 Subject: AntiOnline Greetings: Ok, my little AntiSpider is probably archiving the hell out of your site right now. Hey, even YOU, as much as you dislike me, have to admit our content has been pretty good lately. Especially the stuff we put up just today. Yours In CyberSpace, John Vranesevich Founder, AntiOnline =-= [On Feb 28, I report a bug in AntiSearch. I learn that AntiOnline did not develop it. Did the bug get fixed? No.] From: John Vranesevich (JP@AntiOnline.com) To: mea culpa (email@example.com) Date: Sun, 28 Feb 1999 22:43:58 -0500 Subject: Re: antibot bug? Greetings: Piece of shit bot. Spent a fortune on the thing, and it's pulling this. Haha, oh well, i'll check it out. Yours In CyberSpace, John Vranesevich Founder, AntiOnline At 08:21 PM 2/28/99 -0700, you wrote: > >126.96.36.199 - - [28/Feb/1999:20:11:02 -0700] "HEAD /anchordesk/ >HTTP/1.0" 404 0 "-" "Phantom/2.1 AntiBot" >188.8.131.52 - - [28/Feb/1999:20:11:09 -0700] "HEAD /zdnn/personal.html >HTTP/1.0" 404 0 "-" "Phantom/2.1 AntiBot" > >Obviously attrition.org != zdnn :) I think it is getting confused on >which site to fetch from. > >mea_culpa >www.attrition.org =-= [And now? AntiBot still continued to flood us with invalid requests. Looking closely, we can see it attempting to archive something from a "livewire" site, more 'zdnn', and repeated attempts at web pages that were never there, are not linked to, and have no logical thread to be retrieved. These repeated access attempts flood our logs and waste our bandwdith and CPU time. Yet AntiOnline blames US for foul web plage?] A portion of the error log showing AntiBot going haywire. Between [Sat Jun 5 05:42:25 1999] and [Sun Jun 6 05:00:55 1999], AntiOnline was responsible for at least 1502 errors. forced /home/web/negation# ls 036.log -rw-r--r-- 1 root root 201856 Jul 3 06:34 036.log forced /home/web/negation# wc -l 036.log 1502 036.log forced /home/web/negation# See the whole log if you're bored.