Hmm, I haven't really been following up on this. And I don't plan on reading everything, too busy... but I read the first e-mail. I maintain servers that get slashdotted... and my solution to all the failed ssh attempts on these servers was telling sshd to listen on port 443 (server doesn't use https). No more failed attempts :)
<br><br><div><span class="gmail_quote">On 8/8/06, <b class="gmail_sendername">Jeff Carlson</b> <<a href="mailto:jeff@ultimateevil.org">jeff@ultimateevil.org</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;">
James Neff wrote:<br>> Chances are these are script kiddies looking for something fun to do.<br>> Or, they are folks looking for an FTP site to host their Warez stuff.<br><br>Or more likely either use your computer to attack even more hosts, or to
<br>have you join an army of zombie spam-bots.<br><br>> I wrote a script that went through and pulled out the IP addresses from<br>> the log files and added them to my iptables drop list. I also<br>> researched some of them, with the help of WHOIS from Network Solutions
<br>> web pages, and found the ones coming from eastern Europe and Asia. I<br>> banned entire subnets (some */7) from ever getting to my network again.<br><br>There already exist several resources to figure out which network
<br>authority or country is responsible for any IP range. First is<br><a href="http://www.iana.org/assignments/ipv4-address-space">http://www.iana.org/assignments/ipv4-address-space</a> which lists what<br>authority is responsible for every */8 block. Next is
<br><a href="http://blackholes.us">http://blackholes.us</a> which has zone files available via rsync for every<br>country. The supplied zone files are in formats for tcp_wrappers, a<br>plain text format, and a format for a particular DNS server used as a
<br>blackhole server. I have some scripts for converting this data to BIND<br>format if anyone wants them.<br><br>> If you have spare time, you could call the ISP's tech support line<br>> (lookup on Network Soultions' WHOIS page) and threaten litigation if
<br>> they do not police thier own network. This will only work for US based<br>> ISP's. I sent out a few "cease and assist" e-mails to the abuse e-mail<br>> address of several ISP's and one of them called me right back to
<br>> appologize.<br><br>Just about any Unix or Linux has a whois command, so why bother using<br>NetSol's web page?<br><br>> I always thought it would be fun to write a script (somehow trigger it<br>> by the ssh dameon upon receiving a failed login attempt) that would
<br>> automatically portscan and DoS on the offending client.<br><br>DenyHosts can trigger an extension program that receives the IP address<br>of the attacker as *argv[1]. You could do pretty much anything, do a<br>whois lookup, get the ISP name, send email to abuse@, etc. Note that
<br>portscanning is legal, however performing a DoS attack may be regarded<br>as illegal.<br></blockquote></div><br><br clear="all"><br>-- <br>Matthew Gallizzi