Soldato
- Joined
- 8 Mar 2006
- Posts
- 13,300
- Location
- Near Winchester
Mandate key authentication on your SSH. Then keep your private key safe.
I will say one thing about the network security that you've got - NAT isn't enough. I had a linux box and didn't bother overly with security but didn't allow samba and had a complex password. Woke up one morning to find that it had been accessed via SSH and all the passwords changed - was a nightmare to fix. I was behind NAT, firewall AND had a dynamic I.P. address. Set your SSH port (if you run an SSH server) to something other than 22, it stops the automated scripts that packet kiddies seem to use from finding you so easily.
Don't give root permissions over samba - it's just a question of setting your directory masks properly. A code of 777 gives full permission to all users and groups. A quick chmod and/or chown of anything else to the relevant code is a lot easier than having to completely reinstall a system thats been rootkitted.
Because he was port forwarding port 22 and they cracked his username/pass.