-
-
Notifications
You must be signed in to change notification settings - Fork 356
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
Orbot ignores Isolate destination addresses #708
Comments
Reporting this was on my todo list as well. I looked at it a while back and it looked like the isolation was enabled on socks:
but it's missing for transparently proxied connections. It should be enabled there too:
|
I thought this worked but oddly enough I can reproduce the issue on SOCKS too. |
@pgerber I assume that even though the flags are added to the string somewhere in the code, they are not passed to the Tor client and thus it uses the defaults. I feel like Orbot is ignoring the settings for some reason, see #709 for more details. |
@pgerber You're right, adding Thanks everyone for reporting here |
@bitmold just letting you know that I'm still able to reproduce this issue, both in VPN mode and when using Orbot as a proxy. After updating to newest release I cleared storage to make sure that Orbot starts from fresh state. |
Yes this issue wasn't fixed in the latest release. There needs to be a new release of Tor android and a new orbot release that's still in progress to fix this |
I thought that "add IsolateDestAddr to TransPort in torrc" (from changelog) was supposed to fix the issue, my bad. |
Software & Hardware
Steps To Reproduce
Isolate destination addresses
in Orbot.Always-on VPN
andBlock connections without VPN
) or use127.0.0.1:9050
as a proxy. The bug is reproductible in both cases.Additional Informations
I checked that this issue is reproductible in Privacy Browser 3.10.1, Bromite 102.0.5005.96 and Vanadium 103.0.5060.71. Another user confirmed that issue is reproductible on DivestOS ROM (Android 11).
The text was updated successfully, but these errors were encountered: