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

IP Leak on brave browser #4

Open
IUseNixOSBTW opened this issue Oct 19, 2024 · 4 comments
Open

IP Leak on brave browser #4

IUseNixOSBTW opened this issue Oct 19, 2024 · 4 comments

Comments

@IUseNixOSBTW
Copy link

Likely affects all chromium browsers. Steps to recreate:

  1. Make sure extension is set to auto connect
  2. Open a website such as browserleaks.com/ip as soon as the browser starts, you may need to set it as a bookmark or set it as the startup page if you are not fast enough
  3. See your real ip leak

After about a second when the extension loads the ip no longer leaks. This is the fault of your extension because windscribe extension does not leak under the same test.

@kylekatarnls
Copy link
Member

Hello,

Windscribe addon is using manifest v2, which mean at some point it will no longer be possible to use it as you can see on their chrome store page.

Sadly, manifest v3 the new norm (enforced for extension landing on the store nowadays including ours) has significantly changed the way extension can control proxy settings of the browser.

So this bug is due to a known limitation of the browser proxy API. For severe threat model, I'd recommend to have also the desktop app on, or to ensure no sensible tabs are open before the extension icon shows the plain green "protected" state.

We try to find alternative ways to bypass this limitation but it's not possible to use the mechanisms that can be found in windscribe or other manifest v2 for that.

@IUseNixOSBTW
Copy link
Author

Thank you for sharing this information, it is very helpful. I would like to ask about one more thing. I noticed the same bug happens on firefox with both proton and windscribe extensions and obviously firefox still has mv2. Is this a limitation in the firefox proxy api or is it fixable?

@IUseNixOSBTW
Copy link
Author

I did some more testing and the hide.me proxy extension for firefox does not leak in the test I described so it appears to be possible to fix for the firefox proton extension. I hope you can take a look and fix this for firefox atleast.

@funnyalcoholic
Copy link

I am having the same issue on firefox. My ip will leak for a few seconds after opening the browser. @kylekatarnls any idea if you can get fix this for firefox? It sounds like firefoxs manifest v3 is less restrictive:

Firefox MV3 continues to support blocking Web Request
Firefox MV3 offers Event Pages as the background script in lieu of service workers
Over subsequent releases next year, we’ll continue to expand Firefox MV3 compatibility.
https://blog.mozilla.org/addons/2022/11/17/manifest-v3-signing-available-november-21-on-firefox-nightly/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants