91
For users with public facing services: How does the current explosion of AI-discovered vulnerabilities affect your threat model and willingness to be public facing? (lemmy.ml)
submitted 2 weeks ago by to c/selfhosted@lemmy.world
63 comments fedilink hide all child comments
 

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
[–] 1 point 2 weeks ago (3 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

    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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 2 weeks ago (1 child)

    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!

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •