Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request] Connection-specific VPN settings #7320

Open
8 of 10 tasks
wisp3rwind opened this issue Dec 10, 2024 · 1 comment
Open
8 of 10 tasks

[Feature request] Connection-specific VPN settings #7320

wisp3rwind opened this issue Dec 10, 2024 · 1 comment
Labels
feature request For issues asking for new features

Comments

@wisp3rwind
Copy link

I have checked if others have suggested this already

  • I have checked this issue tracker to see if others have reported similar issues.

Feature description

I'd appreciate if Mullvad would offer connection-specific overrides for all/most VPN settings. Specifically, I would have had a use for this with

  • local network sharing (should only be enabled in trusted networks where I have a need for it, e.g. at home or maybe at a friend's place)
  • UDP-over-TCP (only required for networks which block UDP, e.g. some public Wifis, but not my home network)

but I think it makes sense for several other settings as well.

Currently, anytime the necessity to change these settings (away from a secure and performant default) arises, I'll usually proceed via:

  • some debugging of the present networking issues until realizing it's the VPN,
  • a bunch of clicks to change settings,
  • use the network,
  • frequently forget to change the settings back (which might compromise security or performance when connecting to another network).

By making such setting adaptations per-network, these issues would be remedied to a large extent, for a better UX and effectively improved security.

In #3218, some concerns regarding security have been voiced. However, at least in my case, the real concern is insecure public Wifis rather than someone spoofing a BSSID I trust.
Anyone who actually fears a targeted spoofing attack can simply not use connection-specific settings, and appropriate warnings in the UI could create the awareness for this.

Some further ideas to in this regard:

  • there should be an interface to review connection-specific settings at a glance, making it easy to revoke them when deemed outdated
  • one could consider expiry timers (i.e. disable a connection-specific setting when it has not been used in a certain amount of time)

Related feature requests are:

Alternative solutions

I don't think there's a real alternative: This really needs to be as automated as possible, otherwise, I'll inevitably forget to change settings back. Usually, I realize this only a long time afterwards, for example when seeing unexpected network devices discovered by the file manager (i.e. too late).

Type of feature

  • Better privacy/anonymity
  • Better at circumventing censorship
  • Easier to use
  • Other

Operating System

  • Android
  • iOS
  • Windows
  • macOS
  • Linux
@wisp3rwind wisp3rwind added the feature request For issues asking for new features label Dec 10, 2024
@MarkusPettersson98
Copy link
Contributor

Hello! Thanks for your detailed feature request! 🙌

We'll keep an eye on the interest from the community on this. We know that similar feature requests have been made before, so it's not an esoteric request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request For issues asking for new features
Projects
None yet
Development

No branches or pull requests

2 participants