Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add More Connection Options #4

Closed
HardenedSteel opened this issue Mar 2, 2022 · 6 comments
Closed

Add More Connection Options #4

HardenedSteel opened this issue Mar 2, 2022 · 6 comments

Comments

@HardenedSteel
Copy link
Contributor

User may want don't use Tor and may use proxy but it's not possible. That feature would be useful

@ghost
Copy link

ghost commented Mar 9, 2022

Perhaps I2P/i2pd support could be an option too for the future.

@tehradamant
Copy link

I would also like to request more options. My country actively blocks tor and the only way I can connect is by requesting bridges from tor. I'd like to have an ability to enter said bridges and also it would be nice to have a feature to use a proxy. As of right now I literally can't even try to use this wallet at all.

@tobtoht
Copy link
Contributor

tobtoht commented May 28, 2022

Thanks for the feedback. I will look into adding support for bridges.

As of right now I literally can't even try to use this wallet at all.

You can connect to nodes and sync your wallet without Tor if you click the Tor icon in the statusbar and select "Route all traffic over Tor, except traffic to node". Some wallet functionality that depends on the websocket onion service will not work, however.

@WofWca
Copy link

WofWca commented Aug 27, 2022

Regarding Tor bridges:

  • Workaround: launch Tor Browser (with bridges set up), and in the Feather wallet's Tor settings check "Never start bundled Tor" and set port to 9150, like so:

    image

    I believe this will share the Tor Browser session with a Feather wallet session. I don't know if it affects privacy in other ways.

  • I have tried to add the bridges to the torrc file that Feather wallet tries to look up, but it said something like "pluggable transport obfs4 is not supported".

@HardenedSteel
Copy link
Contributor Author

Just tested and you can use Feather wallet with I2P by following this guide: http://a6oqn7gevseuek3akchgzzjkf5qkh5pdj56jjlqtuynsj2krg7wq.b32.i2p/

@maltfield
Copy link

maltfield commented Jan 16, 2023

One of the reasons I prefer Feather over other wallets is because I can trust that it won't send private information out without Tor. If you're going to allow Tor to be bypassed, then:

  1. This should never be the default behaviour,
  2. The button to disable Tor should display a big scary warning message about the privacy risks to the user, and
  3. The change will not be applied until the user clicks a "Yes, I accept the risks" (or similar) button on the warning message's prompt

In general, I think more functionality is good --- but we should intentionally raise the barrier of entry to let a user bypass Tor. Consider the UX that TAILs uses for the "Unsafe Browser" (used only for bypassing captive portals), for example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants