93
submitted 3 days ago by Ferrous@lemmy.ml to c/selfhosted@lemmy.world

PHP, TLS, etc.. We appear to be facing a tsunami of vulnerabilities being discovered in record time. Further, the window to act on these vulnerabilities has basically closed to zero; hackers' tools now automatically fold the very latest vulnerabilities into their botnets within minutes/hours of discovery. I have always been extremely reluctant to expose any of my services - even with the latest and greatest security tools. My choice to stay totally within the confines of tailscale seems vindicated given this week's news. How are you all taking this?

https://pwn.watch/

you are viewing a single comment's thread
view the rest of the comments
[-] tigerhawkvok@startrek.website 1 points 2 days ago

Yeah, if you use something like Nginx Proxy Manager you can't use the automatic flow, you need to use the token based challenge.

[-] emax_gomax@lemmy.world 2 points 2 days ago* (last edited 2 days ago)

Boo, no idea why acme forces these specific ports. Swapping them seems like a pretty basic obfuscation technique that could help a lot to secure any services.

Edit: actually seems like this might be possible with the dns challenge type. I'm gonna test this out later https://github.com/caddy-dns/porkbun

[-] tigerhawkvok@startrek.website 2 points 2 days ago

It is, that's what I had meant by token based challenge lol. You need a DNS API key for your manager to do it directly, it flags a DNS record with a token to validate ownership. I was just calling it out from memory, sorry!

[-] emax_gomax@lemmy.world 2 points 2 days ago* (last edited 2 days ago)

Much appreciated stranger. Hopefully now I can stop exposing the two most attacked ports in existence from my LAN XD.

this post was submitted on 22 Oct 2026
93 points (97.0% liked)

Selfhosted

63211 readers
490 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