this post was submitted on 10 Apr 2024
41 points (93.6% liked)

Selfhosted

50178 readers
367 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 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
41
Do I Need to Harden SSH over Tor? (self.selfhosted)
submitted 1 year ago by anon2963 to c/selfhosted@lemmy.world
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
[–] AbidanYre@lemmy.world 15 points 1 year ago* (last edited 1 year ago) (20 children)

If you don't have any good reason not to

Spoiler alert: you don't.

[–] marcos@lemmy.world 21 points 1 year ago (8 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.

[–] captain_aggravated@sh.itjust.works 2 points 1 year ago (3 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?

[–] rentar42@kbin.social 1 points 1 year ago

In that scenario I would have a SSH key unencrypted in my home directory that's automatically used. Why would I want to keep typing the password? ;-)

load more comments (2 replies)
load more comments (6 replies)
load more comments (17 replies)