Privacy

2103 readers

400 users here now

Welcome! This is a community for all those who are interested in protecting their privacy.

Rules

PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!

Be civil and no prejudice
Don't promote big-tech software
No reposting of news that was already posted
No crypto, blockchain, NFTs
No Xitter links (if absolutely necessary, use xcancel)

Related communities:

Some of these are only vaguely related, but great communities.

founded 5 months ago

MODERATORS

[email protected]

If you use Mullvad, do you use the "Quantum-resistant" option in official client? (lemmy.sdf.org)

submitted 1 month ago by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

I've always had it on, but it's kind of a pain in the ass. Especially on worse (not necessarily slower) networks.

On laptop it's fine for the most part since the use-case is a bit different, but on a phone it's causing me some annoyances/issues.

With my carrier indoors it takes on average 62 seconds to connect. This is pretty annoying if toggling/switching VPN servers more often.
But when travelling (e.g.: in a train) it can make the difference from slightly spotty signal to almost never being connected successfully, impacting usability.

As such, I often find myself not even using VPN in such cases in the first place.
For comparison, plain Wireguard is done before I can pull away my finger from the "connect" button, usually even on 2G EDGE.

Do you keep this (perhaps a bit paranoid-level) option on?
Even if actually useful in the future, it would only protect traffic recorded from User to VPN anyway.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 15 points 1 month ago

That shouldn't happen. All quantum resistant does is to switch out RSA for ML-KEM. The data transmitted is slightly more, around a KB vs a couple bytes, but that only happens once. The algorithm itself is actually faster.

So something else is going on here. I suspect it has to do with the MTU of your carrier, because the handshake will most likely not fit into a single packet, and then maybe something goes wrong with the related ICMP.