Support will be removed on both client and server side.

The process of removing OpenVPN from our app starts today and may be completed much earlier.

  • MentalEdge
    link
    fedilink
    arrow-up
    158
    arrow-down
    2
    ·
    3 days ago

    TL;DR They are moving to wireguard only.

    I’m ok with that.

    • u/lukmly013 💾 (lemmy.sdf.org)@lemmy.sdf.orgOP
      link
      fedilink
      English
      arrow-up
      70
      ·
      3 days ago

      Except the 5 device limit. With OVPN it means 5 connected devices, with WG it means 5 registered public keys.

      Say you use the official Mullvad app and also setup some 3rd party WG client on your phone. That’s now taking up 2 devices. Or perhaps you do have 6 devices, but you never have more than 2 of them running at once. With WG, that’s still 6 devices regardless of them being connected or not, while with OVPN it will indeed be just 2 devices.

      • communism@lemmy.ml
        link
        fedilink
        arrow-up
        4
        ·
        1 day ago

        That’s true. I use user profiles on GrapheneOS and have to have each profile count as its own device in Mullvad, when obviously I’m not going to be using them simultaneously.

      • PunkiBas@lemmy.world
        link
        fedilink
        arrow-up
        14
        ·
        3 days ago

        This is a great point, if they’re gonna make this change, they should allow unlimited keys (or at least more than 5) and just limit the number of simultaneous devices on wireguard too. If that’s feasable

        • NekuSoul@lemmy.nekusoul.de
          link
          fedilink
          arrow-up
          12
          ·
          2 days ago

          It might be feasible, but it’s a bit awkward to implement because Wireguard is stateless and doesn’t know if a client is offline or just hasn’t sent any traffic for some time.

      • MentalEdge
        link
        fedilink
        arrow-up
        8
        ·
        edit-2
        3 days ago

        That’s a pity.

        Is there something preventing you from having the same key ready for use on more than one device? So that two devices that are never connected at the same time can take turns using the same key?

      • RecallMadness@lemmy.nz
        link
        fedilink
        arrow-up
        1
        ·
        2 days ago

        One of my devices uses three keys because out of the two local servers I have, they seem to go down every other month, so I need a failover.

        • MentalEdge
          link
          fedilink
          arrow-up
          13
          ·
          3 days ago

          I already commented on this, but do they actually block you from setting up multiple devices with the same key?

          I’ve had my own server node for a while, there’s nothing stopping me from using the same key and config on multiple client devices, as long as I don’t connect them at the same time.

          I’m not limited to five keys, obviously, but the keys aren’t device specific. I could set up just one on the server, and then use it everywhere.

          Does Mullwad stop this in some way?

          • ReversalHatchery@beehaw.org
            link
            fedilink
            English
            arrow-up
            5
            ·
            3 days ago

            I already commented on this, but do they actually block you from setting up multiple devices with the same key?

            I don’t think that’s possible to block, but it could lead to problems (responses not arriving) when both devices try to use the same key.

            • MentalEdge
              link
              fedilink
              arrow-up
              8
              ·
              3 days ago

              Well yeah, you’d still have the limitation that you can’t connect multiple devices at the same time. But the idea is that just like before, nothing is actually stopping you from having as many devices as you like ready to go, all able to be used one at a time.

    • AllNewTypeFace@leminal.space
      link
      fedilink
      arrow-up
      25
      arrow-down
      1
      ·
      3 days ago

      Wireguard is more elegant and performant, and has a smaller attack surface. OpenVPN, meanwhile, is a legacy protocol, and retiring it should be a good thing.

        • Rogue@feddit.uk
          link
          fedilink
          arrow-up
          19
          arrow-down
          3
          ·
          edit-2
          3 days ago

          About the same time VPN platforms started migrating away from it

          • EveryMuffinIsNowEncrypted@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            15
            arrow-down
            1
            ·
            edit-2
            3 days ago

            I feel like that’s kind of a case of circular reasoning though: we move away from it because it’s legacy, and it’s legacy because we’re moving away from it… Mind you, I’m no expert on VPNs; this is just something I thought I’d bring to attention here.

            • verdigris@lemmy.ml
              link
              fedilink
              arrow-up
              2
              ·
              1 day ago

              That’s what makes software legacy; it falls out of popularity. Plenty of terminal applications have barely changed since the 80s, but they’re not “legacy” because they’re actively used and maintained.

        • superglue@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          4
          ·
          3 days ago

          Wasn’t aware of this. I’ll check it out! One annoying thing with Mullvad though is the wireguard keys count against your device limit and I already have problems with that. Using OpenVPN didn’t count against the limit. The again I’m also considering switch to Surfshark since its cheaper.

          • shaserlark@sh.itjust.works
            link
            fedilink
            arrow-up
            2
            ·
            edit-2
            3 days ago

            Yeah the device limit is annoying. I switched to AirVPN when Mullvad stopped doing port forwarding and it’s been fine so far. But you’d run into the same issue with the device limit.

            I’m not a network expert so I honestly don’t know the difference between the two protocols enough to say that they’re any benefit of one over the other, but there might be a reason that WireGuard is becoming the default? Idk honestly.

            Anyway, AirVPN still suports port forwarding and supports OpenVPN so might be an alternative for you. They don’t do security audits which is imo sketchy and makes me question if they are honest about their no logs policy, but otoh they have been around for a long time and there hasn’t been any incidence, which makes me think they’re probably good enough for torrenting.

      • ReversalHatchery@beehaw.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 days ago

        sometimes people keep a container for the vpn/proxy, and set up the other one to use the network of the other container