Advertisement Jump to content
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views


Sign in to follow this  


I don't know if you use a *nix. If you do, I'd direct you to your auth.log file. FreeBSD defaults this to /var/log/auth.log

Anyways, everyone I know, gets a dictonary bomb every few days or so (either on the password, or looking for users with weak or no passwords)

Several things to lock this down.
1. Disable root access over ssh. Once logged in with a wheel account, use SU and SUDO to get things done.
2. Ensure that only accounts that need to be logged in via ssh have valid shells. Otherwise point them to nonexistant shells.

There's more especially with firewalls but security is a tricky thing.

Anyways, I found a perl script/cron job that will temporaily ban IP addresses from accessing sshd after n failed logins.
Setting this up is good and bad for security. It becomes possible to DoS the machine by spoofing IP addresses, but as the majority of these attacks are script kiddies or bot nets I'm not to worried about it. Also since it's trivial for me to hook up a keyboard and monitor to the little machine, regaining control and clearing out the DoS spoof is a trivial matter. If your boxes are crosscountry at a colo, you may wish to reconsider this.

Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

By using, you agree to our community Guidelines, Terms of Use, and Privacy Policy. is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!