this post was submitted on 19 Nov 2026
41 points (100.0% liked)

Selfhosted

63928 readers
862 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
 

Someone: "... the new php vulnerability"

Me: "wait what, another one?"

S: "Yes"

I had exposed services for years, never a problem. I don't have time to be on top of all of this. Im going random high port wireguard access only.

you are viewing a single comment's thread
view the rest of the comments
[–] SGG@lemmy.world 3 points 1 hour ago* (last edited 1 hour ago)

Wireguard is a relatively speaking new technology compared to PHP. Less legacy code to worry about.

I do not doubt there will/are vulnerabilities for it, but with any luck they will be few and far between with quick patches