It is really unfortunate that most people that replied to this feel the need to be haughty in their responses. I was simply trying to create a tool to give back to the community. Our servers were comprimised by a tor user and I saw the need to do my best to blacklist such users. If this is not your need, then please respond to me personally with any suggestions you may have, but do not start a public flame war like you are attempting.
<br><br><br>Jason Areff<br>
CISSP, A+, MCSE, Security+<br>
<br>
<br>
----------<br>
security through obscurity isnt security<br>
----------<br><br><br><br><div><span class="gmail_quote">On 6/3/06, <b class="gmail_sendername"><a href="mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu</a></b> <<a href="mailto:Valdis.Kletnieks@vt.edu">Valdis.Kletnieks@vt.edu
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Fri, 02 Jun 2006 23:47:38 CDT, str0ke said:<br>> Umm what about the new ip addresses that are added to the tor network?
<br>><br>> <a href="http://serifos.eecs.harvard.edu/cgi-bin/exit.pl?sortbw=1&addr=1&textonly=1">http://serifos.eecs.harvard.edu/cgi-bin/exit.pl?sortbw=1&addr=1&textonly=1</a><br><br>Ahh.. there we go. Now a wget of that every once in a while, and a little
<br>bit of Perl kung-foo to build an 'addrs.h' file that gets #include'ed and<br>then rebuild the module, and we're getting closer. ;)<br><br>(And don't forget to throw out any alleged exit addresses in your own<br>address space, and any other addresses you really don't want to block.
<br>It's embarassing when a clever hacker uses your own security routines to<br>DoS you ;)<br><br><br></blockquote></div><br>