Title continuation would be “while having limited knowledge of Internet security”.
I have recently set up a small server with a low end computer running debian with the aim to use it as a personal git repository.
I have enabled ssh and was quite surprised at the promptness at which it suffered from brute force attacks and the like.
Then I read that this is quite common and learned about basic security measures to ward off these attacks (lots of questions and duplicates on serverfault deal with it, see for instance this one or this one).
But now I am wondering if all this is worth the effort. I decided to set up my own server mostly for fun : I could just rely on third party solutions such as those offered by gitbucket.org, bettercodes.org, etc.
While part of the fun is about learning about Internet security, I have not enough time to
dedicate to it to become an expert and be almost certain that I took the correct prevention measures.
In order to decide if I will continue to play with this toy project, I would like to know what I really risk in doing so.
For instance, in what extent are the other computers connected to my network threaten as well? Some of these computer are used by people with even lesser knowledge than mine running Windows.
What is the probability that I get into real trouble if I follow basic guidelines such as strong password, disabled root access for ssh, non standard port for ssh and possibly disabling password login and using one of fail2ban, denyhosts or iptables rules?
Put another way, is there some big bad wolves I should fear or is it all mostly about shooing away script kiddies?
Best Answer
IMO SSH is one of the safest things to have listen on the open internet. If you're really concerned have it listen on a non-standard high end port. I'd still have a (device level) firewall between your box and the actual Internet and just use port forwarding for SSH but that's a precaution against other services. SSH itself is pretty damn solid.
I have had people hit my home SSH server occasionally (open to Time Warner Cable). Never had an actual impact.
Some additional things you can do to make SSH safer are prevent repeated attempts from the same IP address for a home machine something like
in /etc/ssh/sshd_config which will restrict how many connections can be created in a row before logging in successfully.