Option to set proxy settings

[anon238]

[goosewobbler]

@anon238 could you add some more specifics to this ticket? Which proxy settings? What is the usecase?

[anon238]

I’m looking for an Ethereum (mostly dapp) wallet for Tails. If you could implement socks5 settings then I can route it through Tor. Feather wallet and Electrum both supports this.

[goosewobbler]

Feather Wallet is C++ based and Electrum is Python, but it looks like it is possible to enable socks5 in Electron, though not with authentication:
https://stackoverflow.com/questions/66867529/how-to-set-the-socks5-proxy-in-electron
https://www.electronjs.org/docs/latest/api/command-line-switches#--proxy-serveraddressport

We have had some users in our Discord try Frame with Tails, they ran into issues getting the Frame Companion browser extension to recognise Frame -- this is either a Tails restriction on the localhost port 1248 which Frame uses to connect, or a similar issue with Tor Browser restricting access to this port. More investigation is required, any community help with this or insight into the problem would be greatly appreciated.

[Crypt0-Bear]

I will add some context.

So usually in the tails setup, applications will route through tor. The easiest settings that this compares to is in an enterprise environment where there is a corporate proxy.

The correct way to handle this is to provide a flag that sets the application proxy as socks5 and uses dns through the proxy. Then a user can connect their proxy to
localhost:9050 (the tor service).

Then all outbound connections will work through the proxy.

There is an additional benefit that trezor suite already uses tor for backend addresses. So enabling this helps simplify some of the suite connectivity as well as provide more privacy as the user can control how the application connects to the outside world.