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

VPN extensions not working in expected manner [solved: uBO CNAME uncloaking: use a system-wide VPN] #1401

Closed
kaurav99 opened this issue Mar 20, 2022 · 9 comments
Labels

Comments

@kaurav99
Copy link

🟥 https://github.com/arkenfox/user.js/wiki/5.2-Troubleshooting
☑️ I have read the troubleshooting guide, done the checks and confirmed this is caused by arkenfox

  • unchecked issues may will be closed as invalid

🟪 REQUIRED INFO

  • Browser version & OS: Windows | 98.0.1 (64-bit)
  • Steps to Reproduce (STR):
  • Expected result : VPN Extensions to work exactly the way they are intended to.
  • Actual result: Not giving expected result.
  • Console errors and warnings:
  • Anything else you deem worth mentioning: If anything in user.js that is restricting those extensions to work efficiently and can be changed to achieve the expected result.

In hardened profile VPNs taking too much time to get connect to the server and even if they get connect by chance there is a DNS leak (I used https://www.expressvpn.com/dns-leak-test for the test)
To know if it was a problem with user.js, I created a separate profile and only added the one extension i.e. Windscribe to test if I get the same issue but in new profile it was working fine and in test there was no local IP leak.
Attaching screenshots of both the profiles, please help me in this,
Thank you.

New profile Without arkenfox user.js
New profile Without arkenfox user.js

Hardened profile with arkenfox user.js
Hardened_profile_arkenfox_userdotjs

@fxbrit
Copy link
Collaborator

fxbrit commented Mar 20, 2022

this seems pretty hard to reproduce, given that I don't expect many to use a VPN extension (why do these even exist? how do they actually work behind the scene?), leave alone that specific one..

if it's nothing more than a proxy, the user.js is instead set-up to force dns queries inside it, so I would expect the exact opposite.

@Thorin-Oakenpants
Copy link
Contributor

FF98 new profile with arkenfox master

vpn

vpn2

vpn3

@Thorin-Oakenpants
Copy link
Contributor

I fail to see how this has anything to do with AF to be honest. Use a proper VPN. My other observation, last night, was that on Nightly (where I have about 20 pref changes like sanitizing, nothing major - i.e no arkenfox), I got the opposite results

@icpantsparti2
Copy link
Contributor

I tried it with default arkenfox without issue, but if you have uBlock Origin running look at the "Uncloak canonical names" setting: https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#uncloak-canonical-names

@Thorin-Oakenpants
Copy link
Contributor

Thorin-Oakenpants commented Mar 21, 2022

interesting, my nightly has uBO

nightly with uBO enabled = shows dns exposed x 6
nightly with uBO enabled but disabled for test site = shows dns exposed x 6
nightly with uBO enabled but uncloak canonical names unchecked in settings = no leak
nightly with uBO disabled = no leak

all tests done with restarts and full sanitizing in between

@Thorin-Oakenpants
Copy link
Contributor

To know if it was a problem with user.js, I created a separate profile and only added the one extension i.e. Windscribe to test if I get the same issue but in new profile it was working fine and in test there was no local IP leak.

But then OP didn't say they then added arkenfox to that new profile and tested again. OP only said they had a problem in their hardened profile. OP did not show that arkenfox caused this issue. Unless OP says otherwise, this is invalid

@Thorin-Oakenpants Thorin-Oakenpants changed the title VPN extensions not working in expected manner. VPN extensions not working in expected manner [solved: uBO CNAME uncloaking: use a system-wide VPN] Mar 21, 2022
@Thorin-Oakenpants
Copy link
Contributor

despite OP not following instructions - AF does recommend uBO, so I'll mark this as answered so it's more visible

@kaurav99
Copy link
Author

Yeah, after disabling Uncloak canonical names it is working perfectly, and really sorry for not mentioning that it was working fine with edge, brave and in Firefox hardened profile too but with system-wide VPN.

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

No branches or pull requests

4 participants