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.

  • atmur@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    2 天前

    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…

    • CorrectAlias@piefed.blahaj.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 小时前

      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.

    • njordomir@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      18 小时前

      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.

    • Guiorgy@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 天前

      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.