On Fri, Jan 9, 2015 at 5:07 PM, Reindl Harald <h.rei...@thelounge.net> wrote:
> for that i would seek a dedicated honeypot-service listening on port 22 > with it's own logging and have the real sshd with key-only auth on a > non-default port > > https://code.google.com/p/kippo/ > https://github.com/desaster/kippo > > that has also the benefit even in case of a bug in sshd itself that you > have all the crap on a different code base not be real sshd at all > Thanks for the links, I had only used Kojoney in the past. I will give it a go as soon as possible. But now I have another question, well actually it is the same one, but from a different point of view: Is it possible to misconfigure sshd in such a way that a client who tries to connect to the server from an unauthorized system keeps typing their username and password, wondering why they can't get in? If yes, which directives in sshd_config should be changed to avoid this problem?
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
