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.

all 49 comments

sorted by: hot top controversial new old
[–] 39 points 2 days ago (6 children)

I do the same. It helps me sleep a little better

  • source
  • hideshow 6 child comments
  • [–] 30 points 2 days ago (5 children)

    I do the same, SSH behind WireGuard and my public facing website/services are on a higher port number

    The only traffic I see is from myself or the people I know personally. It prevents a hobby from turning into a job

    However I do feel like the response to all these vulnerabilities are getting overblown. From my understanding, a lot of them require very specific conditions for exploits to work. It seems like AI pushers are trying to pad their security resumes with fancy websites. But I'm not a security expert so I could be wrong

    I instead keep my system simple and mininal to avoid any headaches or at least keep them to a minimum

  • source
  • parent
  • hideshow 5 child comments
  • [–] 20 points 2 days ago* (1 child)

    A lot of the CVEs lately have been rather overhyped, true, but malicious activity online has skyrocketed in the past month alone. I work in a sizeable SaaS shop and we're seeing a huge spike in curated highly intentful attacks on our systems.

    The problem isn't with the CVEs themselves, it's more about response time now, bc any vulnerability, published or discovered, are getting exploited at faster rates than mitigation can keep up with. That window is the scary part.

    It has made me paranoid enough to completely shut off port forwarding on my home router (I only had a handful being routed internally to Traefik). I'm now trying to find the time to properly set it up with cloudflared and mTLS... I'm tired guys 😭

  • source
  • parent
  • hideshow 1 child comment
  • I may be a bit sheltered. For the last 5 years I have been cutting myself off from subscription services and reduced my online/digital service needs. I won't say I predicted where we are today but I did see a trend not long after the COVID lockdowns and decided to reevaluate my expectations about technology and the internet. I've drastically lowered my expectations so I can still enjoy this technology a little bit even when everything seems so disappointing lately

    I've also opted for extreme minimalism for my selfhosted server. Simple operating system, minimal programs/tools installed and no databases. I don't even use a git forge. Instead I clone my Codeberg repos to a basic file server run by my reverse proxy. I don't need any collaboration tools when all I want is my project repos to be accessible online. My future blog project will just be markdown files rendered to HTML to keep it as simple as can be (the inspiration). I've been so unstressed about all the new vulnerabilities that I've been peacefully enjoying the projections I am currently working on

  • source
  • parent
  • [–] 8 points 2 days ago (1 child)

    I love the CVE's that go with physical access to the machine a ..... I mean if they have physical access to my machine they can do whatever they want anyways unless it is really locked down.

  • source
  • parent
  • hideshow 1 child comment
  • My server is a used Raspberry Pi 5 with an old USB3 portable harddrive. If anyone wanted root access, all they need is a Linux Mint live USB... So you're right, if they have physical access already, they can do whatever they like to it

    The only really important information on there is the token for TLS certificate challenges. Everything else on there was hand selected to be shared knowledge. Who knows, maybe they can make use of all those survival books I have hosted from my basic little file server

  • source
  • parent
  • [–] 30 points 2 days ago (4 children)

    Why a random high port? Wireguard doesn't respond on its port unless it gets its "handshake", so acts as stealth.

  • source
  • hideshow 4 child comments
  • [–] [S] 22 points 2 days ago (3 children)

    Because im trying to be cool.

    But serious. If ever a wireguard vulnerability is found, which I is not very probable and a terrifying prospect, the default port will be the main target.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 19 points 2 days ago

    Same here, for quite a while. There is no reason for my NextCloud server to be exposed on the public internet. I still have access to it from everything via Tailscale and it works perfectly.

  • source
  • [–] 13 points 2 days ago (3 children)

    I already do this but I get nervus still with this second php thingy. Knock on wood that wireguard vulnerabities are not going to come into the thing.

  • source
  • hideshow 3 child comments
  • [–] 11 points 2 days 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

  • source
  • parent
  • [–] 10 points 2 days ago

    Wireguard was actively designed to have fewer vulns. There's very little configuration available which dramatically reduces the number of scenarios a developer needs to consider when writing software. There are surely issues because no piece of software is perfect, but that was at least a stated design goal.

  • source
  • parent
  • [–] 13 points 2 days ago* (4 children)

    I'm on the fence. I have auto updates on, I have my services routed through Cloudflare's proxy (besides Jellyfin) with rules blocking any connection from outside of my country, all running as rootless containers, all passing every security scan I've thrown at them... But I still have a sinking feeling something's gonna bite me.

    But I really like being able to share links or connect without faffing with a VPN...

  • source
  • hideshow 4 child comments
  • [–] 3 points 1 day ago

    I get that. I have my Nextcloud locked down pretty good. It's my only public facing service. But even with an A+ on Nextcloud's security scan and best practices on everything else, it still makes me a bit uncomfortable. Anything else goes over Wireguard. Everyone has a different level of comfort I guess. I'm a fairly careful individual when it comes to unrelated non-tech life decisions too. Some things just don't belong on the web... or in an AI infested operating system.

  • source
  • parent
  • [–] 2 points 2 days ago*

    Every solution has its pros and cons. If you rely on something that requires public access (like randomly sharing access with others) than this is not a solution for you. With that said, you can go hybrid, anything high risk that you will never share with others (or only with a few predefined set of people that you can share a VPN config with) can go behind a VPN, anything you intend to share with others stays public but goes into a VM on a separate VLAN with restricted access to stuff to minimize the blast radius should sh*t go down. Personally this is what I'm trying to do, most things have been moved behind VPNs, only a few things remain public and I'm slowly moving them to separate VMs in a restricted network.

  • source
  • parent
  • If you're using cloudflare tunnels, you might consider using mTLS, which effectively blocks (or provides a challenge, depending on how you configure your WAF rules) anything without your mTLS. The catch is that generally, apps need to support mTLS themselves, although this is not the case for browser based access.

  • source
  • parent
  • [–] 5 points 2 days ago

    The keycloak/java one is a big deal since it was used to get into a few places.

  • source
  • [–] 4 points 2 days ago (1 child)

    I fear this will eventually become the only way to safely selfhost for pretty much everyone. :/

  • source
  • hideshow 1 child comment
  • [–] 1 point 2 days ago

    It has always been the safest way to host private apps.

    I don't mean WG specifically (although that's a great method) but I think everybody should be using some second layer that's enforced on a different level from the app itself: mTLS, OAuth, basic auth in the reverse proxy, even some geoblocking, anything.

  • source
  • parent
  • [–] 3 points 2 days ago

    Thanks god I’m not using any public-facing PHP applications anymore.

  • source
  • [–] 2 points 2 days ago

    I’ve been doing this since I set up remote access. Nobody else should ever be using this but me, so why bother exposing anything?

    Writing iptables isn’t even that hard

  • source
  • [–] 3 points 2 days ago

    I'm honestly considering this for some of my small business customers too, expose their services other than their standard websites on high ports, that way it's generally only expected business contacts who will be making connections to those services.

    AI has so many customers flapping about security at the moment.

  • source
  • [–] 3 points 1 day ago

    same here more or less, at home nothing is open anymore, everything goes through tailscale and a raspberry pi that also does the wake on lan for the big pc when I need it. the only thing exposed is a hetzner vps with a small browser game, and there I keep it boring, ufw with just 80 and 443 (and rtmp for a stream relay), caddy in front, the node app and postgres only reachable from inside the box. I guess that's the trade off that works for me, whatever strangers need to reach lives on one machine I watch closely, the rest stays behind the vpn

  • source
  • [–] [B] 2 points 2 days ago* (last edited 12 hours ago)

    Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

    Fewer Letters More Letters
    Git Popular version control system, primarily for code
    SSH Secure Shell for remote terminal access
    TLS Transport Layer Security, supersedes SSL
    UDP User Datagram Protocol, for real-time communications
    VPN Virtual Private Network
    nginx Popular HTTP server

    6 acronyms in this thread; the most compressed thread commented on today has 9 acronyms.

    [Thread #173 for this comm, first seen 20th Nov 2026, 11:40] [FAQ] [Full list] [Contact] [Source code]

  • source
  • [–] 2 points 2 days ago

    With the recent nginx vulns I was just thinking about all the docker containers that are sitting there with a test webpage on an ancient version of nginx. I went and nuked all my test containers to reduce attack surface. But also sticking with VPN or Tailscale.

  • source
  • [–] 6 points 1 day ago (1 child)

    Random high port will not make you any more secure.

    You can use a tool like shodan or censys to quickly get a list of IP:ports with PHP <8.0.

  • source
  • hideshow 1 child comment
  • [–] 15 points 1 day ago

    Wireguard is UDP only. A UDP service doesn't have to answer invalid requests and Wireguard doesn't, unless you present the right key. This means it's basically impossible to tell an open port from one where no service is listening.

  • source
  • parent
  • [–] 2 points 2 days ago

    That's why I opted for Headscale with a Tailscale fallback option. I'm thinking of setting up an old Pi to regularly check an HTML page on Neocities. If the page reads Heads, enable Headscale. If it reads Tails, switch to Tailscale. That way if my Headscale goes down while I'm away, I can change the page, what a bit, then SSH to the Pi via Tailscale and bounce the Headscale server. I can even power cycle the Headscale box via the LAN (Pi) thanks to some nifty JetKVM accessories.

  • source
  • [–] 1 point 1 day ago

    If you had told me 30 years ago that PHP would be responsible for billions of dollars of losses, I would have said, "I TOLD YOU SO!" Haven't run it since I was forced to write it, the worst thing I've ever written in.

  • source
  • [–] -5 points 1 day ago (13 children)

    would you keep your doors unlocked and open 24/7? no? then why would you expose your server publicly?

  • source
  • hideshow 13 child comments
  • [–] 4 points 1 day ago (11 children)

    This doesn’t make any sense lol

  • source
  • parent
  • hideshow 11 child comments
  • [+] -6 points 1 day ago (9 children)

    an open port is to an open door as an unsecured port is to an unlocked door.

    if you open your unsecured ports to the internet you're telling anyone "walking" by that they can "come on in" and to "take or do anything" that they want to.

  • source
  • parent
  • hideshow 9 child comments
  • [–] 3 points 1 day ago* (8 children)

    No? Thats not quite how it works.

  • source
  • parent
  • hideshow 8 child comments
  • [–] 0 points 19 hours ago (7 children)

    you do realize why ports are called ports, right?

    The term port in networking derives from the Latin words porta, meaning "gate," and portus, meaning "harbor." This reflects the concept of ports as entry and exit points for data, similar to how a harbor serves as a docking point for ships.

    now tell me...what would you call a door on a house? a way....a gate....a gateway......oh yeah, a port of entry and exit!

    go back to networking 101.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 0 points 18 hours ago* (last edited 17 hours ago) (6 children)

    Give it a rest Donny, you’re out of your element.

    Your rudimentary understanding of networking and security that exist only in the abrstact aren’t fooling anyone.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 0 points 14 hours ago (5 children)

    small words coming from a schlub on a selfhosting community that has failed to provide anything other than a blunted wit.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 0 points 14 hours ago (4 children)

    Are you referring to yourself here?

  • source
  • parent
  • hideshow 4 child comments
  • [–] 0 points 14 hours ago* (3 children)

    lol

    edit: and still waiting on that cunning wit you're proud of to provide a better explanation.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 0 points 14 hours ago* (2 children)

    Uh your only explanation for the way you think network security works was the etymology of the word “port”.

  • source
  • parent
  • hideshow 2 child comments