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.

  • exu@feditown.com
    link
    fedilink
    English
    arrow-up
    13
    ·
    9 hours 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.

    • groet@feddit.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 hours ago

      Depends on your firewall though. If you have a “default deny” then the random wireguard port will not send a RST package while the closed ports will. But UDP only sends a few RSTs per second so if you do a UDP-portscan, most systems will only send RSTs for the first few ports and then stop. If you scan very slowly you can find a wireguard port, but you can still not know it is wireguard, just that the port is actually open.

      • exu@feditown.com
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        edit-2
        6 hours ago

        Reject is good for internal rules, but externally you should use drop all the time