You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently Elements don't support using a proxy or Tor outside of Element Web flag without authentication.
Describe the solution you'd like
I would like Elements to support configuring a proxy (or in case of Element Android supporting connecting to OrBot directly) without obscure command line flags that don't support proxy authentication.
Additional context
I wrote this section in a text editor before seeing the issue template
I think Element should support avoiding censorship by proxies, especially Tor which by default uses socks5, TCP port 9050 or with Tor Browser 9150.
Currently proxy authentication is not supported even by Element Web, but I consider that an important feature due to Tor's option IsolateSOCKSAuth which allows having different circuits for when different username/password combination is given.
IsolateSOCKSAuth
Don’t share circuits with streams for which different SOCKS authentication was provided. (For HTTPTunnelPort connections, this option looks at the Proxy-Authorization and
X-Tor-Stream-Isolation headers. On by default; you can disable it with NoIsolateSOCKSAuth.)
Any updates on this?
Many of us are unable to use the app in India due to the recent ban. The ISPs are throttling connection, rendering the app unusable without a VPN, it would be much easier if element apps had an inbuilt proxy option like Signal and Telegram.
Is your feature request related to a problem? Please describe.
Currently Elements don't support using a proxy or Tor outside of Element Web flag without authentication.
Describe the solution you'd like
I would like Elements to support configuring a proxy (or in case of Element Android supporting connecting to OrBot directly) without obscure command line flags that don't support proxy authentication.
Additional context
I wrote this section in a text editor before seeing the issue template
I think Element should support avoiding censorship by proxies, especially Tor which by default uses socks5, TCP port 9050 or with Tor Browser 9150.
--proxy-server=socks5://127.0.0.1:9050
which isn't particularly user friendly and no support for authentication)Currently proxy authentication is not supported even by Element Web, but I consider that an important feature due to Tor's option
IsolateSOCKSAuth
which allows having different circuits for when different username/password combination is given.The text was updated successfully, but these errors were encountered: