this post was submitted on 05 Jul 2026
68 points (100.0% liked)

Selfhosted

62233 readers
786 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I have a VPS that I secure as much as possible since the IP is public, but does a wireguard-access-only homelab warrant the same efforts? Those with homelabs like this, what do you do?

you are viewing a single comment's thread
view the rest of the comments
[–] surewhynotlem@lemmy.world 22 points 2 months ago (1 children)

If it's just wireguard on a nonstandard port, then you are pretty much done. It's UDP and won't reply to incorrectly signed packets so it's essentially invisible.

[–] possiblylinux127@lemmy.zip -5 points 2 months ago (2 children)

Putting it on a non standard port will change nothing

[–] surewhynotlem@lemmy.world 15 points 2 months ago (1 children)

Security through obscurity is not sufficient. It's also not nothing.

[–] possiblylinux127@lemmy.zip 4 points 2 months ago (1 children)

Wireguard doesn't respond to port scans so it changes nothing

[–] surewhynotlem@lemmy.world 11 points 2 months ago* (last edited 2 months ago) (1 children)

Assume a security researcher finds a bug in wireguard that, if sent a malformed packet, it can crash the service. Then it would be trivialy easy to send that packet to the default port on every IP address and just crash everything for fun.

It costs me nothing to increment the port by 1 and avoid all that drama.

[–] Cyber@feddit.uk 7 points 2 months ago

And, to be fair, you'll know more about your setup when you don't use the defaults as you have to learn more...

[–] 0x0@infosec.pub 2 points 2 months ago* (last edited 2 months ago) (1 children)

It is going to make fingerprinting more annoying while evading default port scans. That isnt nothing but you do you boo

[–] sandwichsaregood@lemmy.world 1 points 2 months ago

I agree that there is some value to obscurity generally, but Wireguard already evades port scans and fingerprinting. Unless a packet is signed with a known key, it gives no response to traffic, so scanners and fingerprinters see a closed port. You ISP can identify WG traffic while you are connected by inspecting your traffic, but random scanners won't see anything. Look on shodan, you won't see Wireguard.