Hi everybody, I was setting up a proxy in gnome-settings, when I realized that it was socks4, and didn’t see any option to set it to socks5. So is there a simple fix to that, or it is currently impossible using gnome-settings ?
socks5 should work fine.
- The socks:// URL scheme should work for socks5, socks4a, or socks4
- You can force it to use socks5 only using the URL scheme socks5://
Um, emphasis on should. I’ve never tested this before ever. But it ought to work.
I tried to put socks5:// to force it to use socks5, but it doesn’t work, I need socks5 because It’s for using mitmproxy, and it says : Invalid SOCKS version. Expected 0x05, got 0x4
The settings only store URLs. Whether your application actually supports the proxy configuration or not is up to the application itself. So you will want to create a bug report with the mitmproxy developers.
What I mean, is that setting proxy host in gnome-setttings to socks5://, doesn’t force gnome to use socks5, it still uses socks4. It is not a mitmproxy bug, mitmproxy only accept socks5, and when an application using socks5 connect to it, it works perfectly. It’s a gnome-settings’s or glib-networking bug, or more precisely, a missing feature. Or I don’t understand what you say maybe ?
What application(s) are you testing this with?
So far I ran thunderbird, discord, element, firefox, steam, rocketleague.
I don’t think any of these use glib-networking. Maybe it is a libproxy issue? Or maybe some of these applications don’t even use that and look up the proxy in gsettings directly and then always interpret the socks proxy setting as socks4.
None of these are GNOME applications. Try testing an actual GNOME application like Epiphany. GNOME applications generally use GSocketClient and libsoup, and should support socks5.
Whether third-party applications respect your proxy settings or not is up to them. We can’t help with applications that are not ours.
I doubt any of those applications actually use libproxy? Also, like GNOME, libproxy also only provides the configured URLs. It’s not going to help you actually connect to a socks proxy.
1 Like
I’m aware of that. I was just thinking that maybe there could be a bug in libproxy that would cause it to pick a socks4:// URL, but after looking at the code I don’t see how that could happen. So it’s probably an application issue.
Ok, now I understand your point ! It must be that the applications defaults to socks v4, ignoring the socks5:// prefix from the gnome settings. Thanks for your help guys.