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.

  • Reannlegge@lemmy.ca
    link
    fedilink
    English
    arrow-up
    12
    ·
    12 hours ago

    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.

    • Badabinski@kbin.earth
      link
      fedilink
      arrow-up
      6
      ·
      9 hours 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.

    • SGG@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      12 hours 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