Hi! On the official web page for “Proxy Support - Signal Support” they mention that setting a proxy is not supported on the desktop clients.
However, when did such labels ever fully deter skilled Linux users?
My question is, did anyone succeed in rootless SOCKS5 configuration for Signal? I know it can be done with e.g. a new network namespace by executing a series of root commands. For example, like whonix does to put Signal-desktop in Tor. Is there anything a bit more gentle and localized? Ideally I’d include it into a bubblewrap (bwrap) configuration that I already have around.
If you’ve looked into that at any moment but didn’t find any straightforward solutions, please write as well. It’s OK, but still valuable to read.
Thx!
You must log in or register to comment.
If you use a flatpak it may be possible to set the proxy using the http_proxy env variable when launching it.
Do you know if it works with Signal? (Doesn’t seem to be… Dunno why. Static build of the app? Non-http-based transport technology used by Signal?)
I don’t, sorry
No problem; thanks for trying to help!