[bisq-network/bisq] Allow the user to configure Tor before connecting to it (#3010)

GI Jack notifications at github.com
Wed Dec 30 18:18:52 CET 2020


Things of note: For users in some locales, as much as being caught running TOR can put them in significant risk to their person for merely this.

To help these users, TOR has implemented bridges. For particularly keen regimes, public bridges are also known and watched by authorities. These users need to enter custom bridges manually to use TOR.

 If TOR starts, before a bridge is implemented PROPERLY it could leak the fact they are using TOR. This needs to be configured at first run.

For power users, tend to run a dedicated node on a separate host. This is to prevent correlation attacks, as the node stays online 24/7, and improves the strength of the network. Making these can be done with small computers like raspis, or virtual machines on cloud networks, and incorporate a wide array of other privacy technologies like various forms of VPN and proxy.

There should just be radio buttons asking users
1. Standard - just uses as now. Has a note that if someone doesn't know to use this option. This is the default.
2. Bridge - drops down a second set of radio buttons for "default" or "custom" allowing a user to enter their own bridge info
3. External - Drops down a hostname, port, username, password, dialog for an external TOR node. defaults are 127.0.0.1 9050 no username/pw

Big continue button at the bottom to save settings and continue loading. All it would take for newb users is just clicking one button, and everyone else can change settings.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/3010#issuecomment-752695759
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201230/87dfd205/attachment.htm>


More information about the bisq-github mailing list