• Aux@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    8 months ago

    Mate, you dumb? The link cites Microsoft KB. This issue is officially reported BY Microsoft, not by some random people online.

    • TAYRN@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      7
      ·
      8 months ago

      Isn’t it weird that you, also, can’t name a single person who was affected by this?

    • TAYRN@lemmy.world
      link
      fedilink
      arrow-up
      1
      arrow-down
      7
      ·
      8 months ago

      Yeah, but you didn’t bother to actually follow the link or read what it says. There was a bug in Microsoft’s VPN implementation (which no one uses) which affected no one, until they fixed it.

        • TAYRN@lemmy.world
          link
          fedilink
          arrow-up
          1
          arrow-down
          4
          ·
          edit-2
          8 months ago

          I am seriously that dumb. Can you give me an example of someone who used it and was affected by this?

          • Promethiel@lemmy.world
            link
            fedilink
            arrow-up
            3
            ·
            8 months ago

            Disregarding the topic and focusing on semantics for half a second out of pure (and weekend freedom stoned) curiosity, why do you value the anecdotal experience of others–and seemingly in one direction only?

            My Cousin Vinny’s Tomato Canning and Money Laundering Inc, ran by my cousin Vinny and his family of hard looking unrelated men lost VPN access after the last Microsoft update. I’m lying, BUT let’s pretend I’m not, what’s your next weird hill, I’m curious.

          • Aux@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            8 months ago

            Well, I used to use it back in the days. Many VPN providers like NordVPN use IKEv2. Older corporate deployments of Cisco VPN use IPSEC. Should I continue?