3 ms·
"On the back of a napkin, so to speak, and with a number of reasonable assumptions, I calculated that it would take 2.2098499729010715e+28 years to do so, with
by javert 17y ago
"On the back of a napkin, so to speak, and with a number of reasonable assumptions, I calculated that it would take 2.2098499729010715e+28 years to do so, with a 1,000,000-strong botnet constantly hammering away." (That's with a 20-char root pwd. Just make your root pwd strong.)
[1] http://www.mollison.us/blog/2009/10/18/how-hard-is-it-to-brute-force-a-root-password-over-ssh/ http://www.mollison.us/blog/2009/10/18/how-hard-is-it-to-bru...
- dlsspy 17y ago1. Disable root login. 2. Disable passwords. There's no excuse for root logins and passwords are harder to manage and less secure.
- gtani 17y agoI also limit port 22 or whatever to, say, 3 tries a minute (iptables) just so you don't look like low-hanging fruit something like this http://jonsbraindump.blogspot.com/2007/09/iptables-rules-to-lock-out-multiple.html http://jonsbraindump.blogspot.com/2007/09/iptables-rules-to-...
- gtani 17y agoi just saw this on HN, a SSH blacklist http://isc.sans.org/diary.html?storyid=7855 http://isc.sans.org/diary.html?storyid=7855
- scumola 17y agoI use the ssh blacklist utility and it works pretty well. Although it opens up the IPs after 4 days (default), which I don't really liked, so I pumped that up to 14 days which seems to work nicely.