Oxide fails to use Tor SOCKS proxy

[Olivier Tilloy]

I set up Tor on my laptop and modified the system settings to use localhost:9050 as a SOCKS proxy. Applications such as chromium or firefox use it correctly, but a simple oxide webview gives this error page when trying to navigate to any URL:

  Tor is not an HTTP Proxy

  It appears you have configured your web browser to use Tor as an HTTP proxy. This is not correct: Tor is a SOCKS proxy, not an HTTP proxy. Please configure your client accordingly.

  See https://www.torproject.org/documentation.html for more information.

[Olivier Tilloy (osomon)]

Because of bug #1260101, oxide is not permitted to read gsettings, so it’s not getting the proxy configuration from there. I’m guessing it’s getting it from the ALL_PROXY environment variable, whose value is "socks://localhost:9050/".

[Cris Dywan (kalikiana)]

Should applications more generally be aware of the system-wide proxy? There was a discussion at one point around a shallow service that can expose (g)settings that are considered sensible without permitting dconf access.
That service could give the proxy server to applications.

[Olivier Tilloy (osomon)]

That sounds like a good idea, although in that specific case I’m not sure that would make a difference. Oxide is getting the correct configuration (whether it is from gsettings or from an environment variable doesn’t really matter), but it doesn’t seem to be using it correctly.

[Olivier Tilloy (osomon)]

On a side note, running oxide unit tests under this configuration makes a number of them fail.