• Imgonnatrythis@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    I dunno man. I’m convinced that pretty much any mention of VPN these days is just an ad for vpns. That’s with this article looks like.

    • Zaemz@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 months ago

      Yeah, you’re not wrong that the article kinda sets itself up for the “lookit our recommended VPNs” pitch.

      There’s no way Microsoft would purposefully disable VPNs from working. I can guarantee that they require VPNs for thousands of roles in the company, let alone breaking it for government agencies that require VPNs, etc.

      It is good to know that a specific update can break something ahead of time, though. Then at least you can avoid it.

  • BaroqueInMind@kbin.run
    link
    fedilink
    arrow-up
    0
    ·
    2 months ago

    Looks like their policy to prefer cheap labor they hire from Asia rather than paying local U.S. developers a living wage is starting to bite them in the ass.

        • lurch (he/him)@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          2 months ago

          The problem is bureaucratic: Using them with Wine is not the manufacturers intent, so it may break for a while and theres nothing the manufacturer will do to fix it. The companies of the users often don’t dare rely on this. It’s also why some companies require to use redhat or ubuntu for a distro, because they don’t dare running anything without a support contract. They think that way there’s someone external to blame, call for help or sue, if things break. I’m not a fan of this, but encountered it a few times on different jobs. At my current job one of our clients has this with redhat and tbh they actually had to call redhat support twice this year, because their server got messed up during upgrades.

      • sgibson5150@slrpnk.net
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 months ago

        Mmm what?

        WireGuard® is an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. It aims to be faster, simpler, leaner, and more useful than IPsec, while avoiding the massive headache. It intends…

        • Dran@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          2 months ago

          Yeah I’m really curious what his take is going to be on this one lol. Technically it doesn’t have a layer-2 capable bridge mode like other VPN solutions like openvpn, but that’s about all I can think of. It’s still objectively a virtual network, made private by a keypair exchange.

          Probably just blindly paroting something someone told him. Awkward way to learn that one lmao.

  • mindlight@lemm.ee
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 months ago

    PCWorld:

    Microsoft’s latest Windows update breaks VPNs, and there’s no fix

    What Microsoft actually said:

    Windows devices might face VPN connection failures after installing the April 2024 security update, or KB5036893. We are working on a resolution and will provide an update in an upcoming release

    I’m so fed up with everyone trying to make a quick buck on our constant struggle to stay safe.

    • w2tpmf@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      2 months ago

      The reality is that it broke "something* in certain lpt2/ipsec connections using certain authentication protocols, although they haven’t yet specified which particular connection technologies are affected.

      However this does not mean that a blanket affect of ALL VPN connection not working is an issue.

      So far we are unaffected on clients using ipsec and PAP protocol authentication, nor connections using Anyconnect (aka Cisco Secure Connect).

      I have also not seen any affect on private VPN clients such as PIA or Nord on machines that have this update.

      I suspect what broke was clients using MSChap, Microsoft’s own protocol for authentication for VPN clients.

      Source: an admin with 200+ client machines with VPN connections that are not impacted after installing this update.