Live data from Hacker News

Securing your Linux web server

medium.com

1–10 of 54 posts

Re: Securing your Linux web server

#6

I have a little checklist I use to cover the basics: https://drewdevault.com/new-server.html

I'm a generalist project manager.

When you say "Disable password login via ssh", what is going to be the login method from this point onwards? Via a personal certificate? Tks

Re: Securing your Linux web server

#7

I have a little checklist I use to cover the basics: https://drewdevault.com/new-server.html

The general advice I've seen is to not host your own server. But I think it would be a great learning experience. If you cover the basics, is your server still extremely vulnerable?

Re: Securing your Linux web server

#8
post #7

I have a little checklist I use to cover the basics: https://drewdevault.com/new-server.html

The general advice I've seen is to not host your own server. But I think it would be a great learning experience. If you cover the basics, is your server still extremely vulnerable?

No, not really. I host plenty of servers, someone's gotta do it.

Re: Securing your Linux web server

#9

I have a little checklist I use to cover the basics: https://drewdevault.com/new-server.html

I'm a generalist project manager. When you say "Disable password login via ssh", what is going to be the login method from this point onwards? Via a personal certificate? Tks

~/.ssh/authorized_keys, which is basically personal certificates.

Re: Securing your Linux web server

#10

I have a little checklist I use to cover the basics: https://drewdevault.com/new-server.html

I'm a generalist project manager. When you say "Disable password login via ssh", what is going to be the login method from this point onwards? Via a personal certificate? Tks

You should be using public key authentication: https://www.digitalocean.com/community/tutorials/how-to-set-...

If you insist on using passwords, make sure you at least install something like fail2ban or denyhosts to block the compromised machines which are hammering your server trying to guess passwords. Clients can see which authentication methods are allowed so they know which machines to attack (i.e., yours, if you allow passwords).

Post reply on HN