• satanmat@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        6 months ago

        Well yeah. That’s kinda the point I was trying to make…

        “It breaks VPNs!!”

        Name one….

        Oh yeah like a whole bUnCh!!!

        Name…… one…

        —- and in two articles I’ve seen they still have not named one. Great work there “journalists”

    • catloaf
      link
      fedilink
      English
      arrow-up
      1
      ·
      6 months ago

      No complaints from anyone at my office. I haven’t heard anything from the general public either. There must be enough people affected because Microsoft noted the issue on the page for the update, but I have no idea who or where they are.

      • wreckedcarzz@lemmy.world
        link
        fedilink
        English
        arrow-up
        14
        arrow-down
        1
        ·
        6 months ago

        So like, the 0 that use that implementation. Like really, IPsec? No openvpn support? No wireguard support? What is this, 2004?

        • zod000@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          6 months ago

          Our sister company had their VPN broken by this and we had to switch to another system. Even though it wasn’t a particularly secure VPN (IPSec), the builtin Windows VPN was extremely reliable and convenience compared to shit like Pulse.

        • refalo@programming.dev
          link
          fedilink
          arrow-up
          3
          arrow-down
          10
          ·
          6 months ago

          I used to live in an apartment with 4 other gay furries

          Somehow I don’t think you are the beacon of corporate experience here