Showing posts with label brute. Show all posts
Showing posts with label brute. Show all posts

Tuesday, October 05, 2010

58.221.32.117 hammering my server

I've been seeing 58.221.32.117 in my logs, especially within the last week or so.  So far, I've 5,356 instances of blocking by the firewall for this particular IP.  All traffic is coming from source port 80 of that IP.  Yes, every single instance was blocked.

Has anyone else seen similar activity from this IP?

A whois shows the following:

IP address [?]: 58.221.32.117 [Whois] [Reverse IP]
IP country code: CN
IP address country: ip address flag China
IP address state: Beijing
IP address city: Beijing
IP address latitude: 39.9289
IP address longitude: 116.3883
ISP of this IP [?]: CHINANET jiangsu province network
Organization: CHINANET jiangsu province network
Local time in China: 2010-10-06 10:29










Wednesday, August 25, 2010

Protect your privates!

Protect your privates!

http://isc.sans.edu/diary.html?storyid=9367


In view of all the brute force attacks still being attempted against Secure Shell (SSH), we have long since been extolling the virtues of forgoing passwords and moving to RSA/DSA keys instead.
While key based login indeed nicely addresses the problem of password guessing attacks, it looks like many a Unix admin has been less than diligent in the implementation. In pretty much every Unix security audit recently, we've come across unprotected or badly protected SSH private keys (id_dsa, id_rsa). Some reside plain flat out in the open, in /tmp and such. Others are found in world-readable tar "backup" archives of user and administrator home directories. Some are even built into home-grown Linux RPM and Solaris PKG packages, ready to be plucked off an install server.