fluffle

Dictionary attacks are by definition not benign. If a compromised host is sending any packets your way, it's best to drop them on the floor where they belong. Then, if for any reason, the person controlling that other host happens to e.g. run portscans to find other services or point nessus / metasploit your way, they are going to have a much harder time of doing so.

Thanks to all, and especially this post, for detailed security recommendations. I hope they convince others that security is important and not to be taken lightly.

I don't really think that security-by-obscurity alone is a good enough solution. I already disable both root logins and passwords on my shell, and have something that tails logs to firewall IPs that are doing nasty things that show up in my logs. It's cute that you assume I'm running Linux though ;-)

I ended up firewalling the entire /14 that /24 was assigned from, because, well, China bothers me...

Wow. I really appreciate that!

I think Go, as a language, makes it much easier to write code that is both well-structured and readable. Of course, I have consumed a non-trivial quantity of the kool-aid, and I am convinced by the arguments that Rob Pike et al. made when outlining their design choices.

Out of interest, has anyone else who's had their personal server mentioned on HN's frontpage noticed an uptick in SSH scans from those lovely folks in the PRC? Certainly did here.

Welp, 221.192.143.73/24 is going in the firewall config.

Hi. Err... had to create a HN account to reply, whyrusleeping on #go-nuts told me this was here.

Feel free to file issues on github and consider that the "source of truth" for my code, and please ignore my site. I don't have time to throw together a web presence, too busy at work ;-)