- cross-posted to:
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ml
We invite you to read the final report of our third security audit, concluded in mid-June 2023, with many fixes deployed late June 2023. Further re-tests and a verification pass was performed during July.
- Radically Open Security found no information leakage or logging of customer data
- RoS discovered 1 High, 6 Elevated, 4 Moderate, 10 Low and 4 info-severity issues during this penetration test.
Forgot one point
- got in trouble for not offering port forwarding anymore
Getting in trouble? It’s more like:
- Server providers threatening to terminate business with Mullvad because some of its users used port forwarding to host contents that meant legal trouble.
- Mullvad chose to terminate support for port forwarding in a transparent way and gave clear dates to prepare. This was done instead of selling off their users or collaborating with whatever legal threats they were facing.
I don’t like it, but at least I understand their business decision. Even if I took my business elsewhere, they have a solid point on transparency.
Agreed, but getting in trouble sounds funnier
Yeah I had to move to another provider over this. It’s sad, I like their policies and services, but it’s a deal breaker.
Good VPN.
Keep it up, guys. Mullvad is since years my go to VPN.
Happy customer for years.
It’s a shame port forwarding is not supported anymore, but I’m thinking of other ways to supply the deficiency instead of switching providers.
What other ways are you referring to, if I may ask?
Having a VPS and routing all traffic between VPS and homeserver using wireguard. It’s often discussed in selfhosting communities where the admin is behind restrictive firewalls and policies (which means no port forwarding) or cannot afford to reveal their home ``IPs