Heinz Diehl wrote:
On 03.10.2009, Cristian Rodríguez wrote:
You can't actually proceed ;-) this is an issue with any network service on planet earth, but you can protect yourself of being cracked by only using public key authentication.
That's how I do it. Maybe I don't get the point, but after reading this whole thread I wonder why folks bother. Don't allow password login, or choose a strong one, and nothing more to it..
I care about the multitude of logs that are caused by the brute-force attacks and which prevent that I can see easily the real attacks. If I let ssh listen on 22, I can't supervise failed login attempts properly. E.g., with logwatch or snort. If it listens on another port, I can do so. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org