#26764: HTTP proxy bug in Orbot 16.0.2-RC-1
--------------------------------+-----------------------
Reporter: soren@… | Owner: n8fr8
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Applications/Orbot | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------+-----------------------
Comment (by n8fr8):
For now, the best place for submitted issues is:
https://github.com/n8fr8/orbot/issues
We are working on consolidating and cleaning up our various trackers. We
are happy to work here on trac, but the volume of notifications and the
fact we don't use this as our core tracker can cause us to miss issues now
and then.
As for this problem specifically, we moved from using Privoxy inside of
Orbot as our HTTP proxy, to using the new, built-in HTTP proxy feature now
available in Tor. Unfortunately, it only supports HTTP Connect proxy
features, which in the case of Android, seem to only work with HTTPS
traffic. For most apps, this is fine and a good requirement, to ensure
traffic moving through Tor is always HTTPS. However, for a browser, which
may still have HTTP traffic, I see how it can cause problems.
The answer is to just guide your users to use the VPN feature, which does
work. You could also consider building your browser from Mozilla's
GeckoView component, which Firefox Focus uses. This supports SOCKS
proxying, which works very well with Tor, and is much more secure than
relying on Android's WebView.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/26764#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online