137

What are common practice's for hardening/securing your server?

posted
by
Avatar
SomeBoyo@feddit.de
in
Avatar
selfhosted@lemmy.world
66 comments
hidereport
Sort:
HotTopControversialNewOld
You are viewing a single thread.
View all comments
Avatar
foggy@lemmy.world
54 points

Setup Fail2ban

Login only with SSH keys. MFA on SSH login. Use SSH proto 2.

Disable passwords, x11 forwarding, root logins

Reduce Idle timeout interval

Limit users’ SSH access

That should be more than enough for the average use case.

permalink
report
reply
Avatar
taladar@sh.itjust.works
13 points

Regular updates are definitely necessary too. Also, if you do limit SSH users to a chroot make sure you limit TCP (port) forwarding too.

permalink
report
parent
reply
Avatar
Possibly linux@lemmy.zip
4 points

Containers can help lock services down if you do it right.

permalink
report
parent
reply
Avatar
MaggiWuerze@feddit.de
3 points

You can have 2FA on ssh?

permalink
report
parent
reply
Avatar
foggy@lemmy.world
1 point

Yep. Use SSH keys, not just protocol.

On connection, it’ll ask for your SSH password (this is different from the users password).

After that with something like authelia in place, you’ll be asked for a 2fa code.

permalink
report
parent
reply
Avatar
MaggiWuerze@feddit.de
0 points

So, no. SSH can’t do 2FA? I would need to set up Authelia and connect through that? I already use ssh keys instead of passwords to connect to my server

permalink
report
parent
reply
Show more comments

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 4.8K

    Monthly active users

  • 3.5K

    Posts

  • 79K

    Comments

Community moderators