this post was submitted on 28 Nov 2023
3 points (100.0% liked)

Self-Hosted Main

502 readers
1 users here now

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.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
 

i want to remotely ssh to my home server, and I was wondering if I could just forward port 22 with disabling password login and use pubkey authentication will be safe enough?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 9 months ago (4 children)

Disable password auth.

Enable key only auth.

Add in TOTP 2FA (google authenticator).

Randomize the port (reduce bots) that forwards to 22.

Configure lockout to block upon 3 failed attempts, for a long duration like 1 year. (Have a backup access on LAN).

Ensure only the highest encryption ciphers are accepted.

Ensure upgrades are applied to sshd at least monthly.

[–] [email protected] 2 points 9 months ago (2 children)

If you are going all out, may as well add hosts.deny and hosts.allow.

[–] [email protected] 1 points 9 months ago (1 children)

Easy to do with known internal networks.

Difficult to manage when roaming.

[–] [email protected] 1 points 9 months ago

Absolutely, just sometimes people forget those tools even exist. Of course, you can easily do the same thing with firewall rules as well.

Also, that was a great tidbit about the pam email notification on successful logon. I haven't seen that one before, thank you!!

[–] [email protected] 1 points 9 months ago

Add port knocking, if we go all out, let's go all out!

[–] [email protected] 1 points 9 months ago

Good summaries. How does the TOTP 2FA article handle drop/reconnects? TOTP needed for each reconnect attempt?

[–] [email protected] 1 points 9 months ago

To help with identifying issues within your SSHd configuration, I recommend using ssh-audit: https://github.com/jtesta/ssh-audit

[–] [email protected] 1 points 9 months ago

Configure lockout to block upon 3 failed attempts

fail2ban