this post was submitted on 10 Apr 2024
42 points (93.8% liked)

Selfhosted

40133 readers
545 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.

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!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
42
Do I Need to Harden SSH over Tor? (infosec.pub)
submitted 7 months ago by [email protected] to c/[email protected]
27 comments fedilink hide all child comments
 

cross-posted from: https://infosec.pub/post/10908807

TLDR:

If I use SSH as a Tor hidden service and do not share the public hostname of that service, do I need any more hardening?

Full Post:

I am planning to setup a clearnet service on a server where my normal "in bound" management will be over SSH tunneled through Wireguard. I also want "out of bound" management in case the incoming ports I am using get blocked and I cannot access my Wireguard tunnel. This is selfhosted on a home network.

I was thinking that I could have an SSH bastion host as a virtual machine, which will expose SSH as a a hidden service. I would SSH into this VM over Tor and then proxy SSH into the host OS from there. As I would only be using this rarely as a backup connection, I do not care about speed or convenience of connecting to it, only that it is always available and secure. Also, I would treat the public hostname like any other secret, as only I need access to it.

Other than setting up secure configs for SSH and Tor themselves, is it worth doing other hardening like running Wireguard over Tor? I know that extra layers of security can't hurt, but I want this backup connection to be as reliable as possible so I want to avoid unneeded complexity.

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

If you don't have any good reason not to, always set your SSH server to only authenticate with keys.

Anything else is irrelevant.

[–] [email protected] 15 points 7 months ago* (last edited 7 months ago) (2 children)

If you don't have any good reason not to

Spoiler alert: you don't.

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

30 character password + fail2ban after one failed attempt. Why not?

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

WCGW?

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

Tell me

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

Accidentally typo your password and get blocked. And if you're tunneling over tor, you've blocked 127.0.0.1 which means now nobody can login.

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

How would is a typo possible if one is using a password manager?

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

Not OP but I've accidentally fingered another key a split second before hitting enter a few times. It's not implausible.

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

True, but I thought we are talking about security here...?

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

30 character

You've gotta pump those numbers, those are rookie numbers. (I have a vps that has several times that figure)

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

Did you read my message? After one failed attempt you will get banned.

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

But

30 characters

:P

[–] [email protected] 21 points 7 months ago (3 children)

This is the internet. If you poke the bear, somebody will come-up with a completely reasonable use case of password authentication that happened once somewhere on the world.

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

Easy. I have servers that are only available on my local network and lots of different devices that I MIGHT want to use to access those servers. I haven't bothered to make sure my key is on EVERY SINGLE DEVICE and some of them, I might not actually even WANT my key on as they're not terribly well secured and they might leave my house (my Windows gaming laptop I haven't used in six months comes to mind).

But for cloud accessible servers... yeah.

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

You know you're allowed (some might even say supposed) to have different keys for different machines. They're basically free to generate and take up to no space.

[–] [email protected] 2 points 7 months ago

I use a different key for every device I need to connect to.

So my phone has separate keys for each SSH server and so does my desktop and laptop.

It's not the most convenient thing in the world but it's not too bad.

Most of the keys are without passphrase but the keys I use to connect to my VPS for example absolutely have a passphrase.

[–] [email protected] 0 points 7 months ago* (last edited 7 months ago)

If there is, I'd love to hear it. But even JuiceSSH on Android has supported keys for like the last decade.

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

Playing with a Raspberry Pi inside my own home network with nothing important going on and I turned the Pi off when I'm done. Like why worry about it at that point?

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

Yeah, that's not a good reason.

It's much easier to authorize a key than to input your password on every kind of interaction.

[–] [email protected] 3 points 7 months ago* (last edited 7 months ago)

Yes, but I usually add my public key to the authorized_keys file and turn off password authentication once i do login with a password. On top of that, I have a sshpass one line command that takes care of this for me. It's much easier than trying to manually type a password for the next time. I save it and just run it every time I think about using password login. Next time I need to ssh, I know the password login is not necessary.

sshpass -p 'PASSWORD' ssh [email protected] "echo '`cat ~/.ssh/id_rsa.pub`' > ~/.ssh/authorized_keys && echo 'Match User !root
PasswordAuthentication no
Match all' > /etc/ssh/sshd_config' && exit" && ssh [email protected]

At the next reboot, your system will now only accept key logins, except for root. I hope the root user password is secure. I don't require it for root because if a hacker does gain shell access, a password(or priv esc exploit) is all they need to gain root shell. It is also a safety net in case you need to login and lost your private key.