Bug in widely used OpenSSH opens servers to password cracking
1–10 of 62 posts
Re: Bug in widely used OpenSSH opens servers to password cracking
#2It's interesting to log failed SSH attempts, I normally get someone trying to brute force access within an hour or two of brining a server up. Changing to a non standard port doesn't deter them for long.
Re: Bug in widely used OpenSSH opens servers to password cracking
#3It's interesting to log failed SSH attempts, I normally get someone trying to brute force access within an hour or two of brining a server up. Changing to a non standard port doesn't deter them for long.
Have you tried fail2ban? It really helps to keep the hacking attempts down on your ssh-server(s), especially if you increase the bantime from the default 600 seconds to a couple of million...
Re: Bug in widely used OpenSSH opens servers to password cracking
#4It's interesting to log failed SSH attempts, I normally get someone trying to brute force access within an hour or two of brining a server up. Changing to a non standard port doesn't deter them for long.
Have you tried fail2ban? It really helps to keep the hacking attempts down on your ssh-server(s), especially if you increase the bantime from the default 600 seconds to a couple of million...
It is all fun and games until you ban yourself for a couple of million seconds...
Far too many people ban themselves with fail2ban.
Re: Bug in widely used OpenSSH opens servers to password cracking
#5Doesn't key authentication protect against this vulnerability?
Re: Bug in widely used OpenSSH opens servers to password cracking
#6Earlier quoted context omitted.
Have you tried fail2ban? It really helps to keep the hacking attempts down on your ssh-server(s), especially if you increase the bantime from the default 600 seconds to a couple of million...
It is all fun and games until you ban yourself for a couple of million seconds... Far too many people ban themselves with fail2ban.
Sharp tools are sharp.
Re: Bug in widely used OpenSSH opens servers to password cracking
#7Doesn't key authentication protect against this vulnerability?
Right. Quote from article: "In some respects, the severity of vulnerability can be viewed as mild. But that assumes OpenSSH users are using a cryptographic key for authentication. Under such an arrangement, only computers with the private key are able to access the Internet-facing server. On top of that, servers themselves should be configured to limit the number of login attempts, and that measure should also go a long way toward making exploitation impractical."
Re: Bug in widely used OpenSSH opens servers to password cracking
#8Earlier quoted context omitted.
Have you tried fail2ban? It really helps to keep the hacking attempts down on your ssh-server(s), especially if you increase the bantime from the default 600 seconds to a couple of million...
It is all fun and games until you ban yourself for a couple of million seconds... Far too many people ban themselves with fail2ban.
I use key-based authentication and fail2ban. Since that won't fail like passwords, it works wonderfully and the chances of my being banned are nil.
Re: Bug in widely used OpenSSH opens servers to password cracking
#9It's interesting to log failed SSH attempts, I normally get someone trying to brute force access within an hour or two of brining a server up. Changing to a non standard port doesn't deter them for long.
Have you tried fail2ban? It really helps to keep the hacking attempts down on your ssh-server(s), especially if you increase the bantime from the default 600 seconds to a couple of million...
Never seen the need for fail2ban when you can do the same thing with a couple of iptables rules.
Re: Bug in widely used OpenSSH opens servers to password cracking
#10It's interesting to log failed SSH attempts, I normally get someone trying to brute force access within an hour or two of brining a server up. Changing to a non standard port doesn't deter them for long.
But what does deter them is port knocking. We went from many attempts per hour to not a single one since adding port knocking to our firewall.
Port knocking has been mentioned before on HN and it generally gets a luke warm to negative response. It completely baffles me, this response.