Tor launcher will detect if the /etc/tor/torrc has the same configuration as the /etc/tor/torrc.orig. If not, user will be asked if they want to abolish the previous customized setting and connect to the Tor network with the setting in /etc/tor/torrc.orig.
Currently, anon-connection-wizard will override the /etc/tor/torrc without asking, which is not good.
Tor launcher will detect if the /etc/tor/torrc has the same configuration as the /etc/tor/torrc.orig. If not, user will be asked if they want to abolish the previous customized setting and connect to the Tor network with the setting in /etc/tor/torrc.orig.
Would it make sense to show them a button âshow configâ or so where they
can view and edit?
Hard question. If anon-connection-wizard one day becomes a fully features Tor controller, then it should be able to read the current state of Tor. That would prefer 1). On the other hand, users may want to persist their setting in anon-connection-wizard. But if they choose public Tor network, then manually set up bridges (or vice versa) using anon-connection-wizard, then manually reverse these settings in the config⌠What is it users expect and want when they start anon-connection-wizard again?
Great idea! Just like what whonix-setup-wizard has been doing.
I like how whonix-setup-wizard shows user the torrc files right before the real connection to the Tor happens. This offers user a feeling of transparency and control to what have been modified by anon-connection-wizard.
I will add a torcr_status page before the Tor status page
It also depends on what Tor users are expected to use anon-connection-wizard. My first thought is that anon-connection-wizard is for basic/inexperience users to let Tor work.
After all, there are so many different commands in Tor manual and we can not implement all the options without scarifying simplicity.
Experienced users can add their own commands via text editor or torrc status page in anon-connection-wizard.
As Patirck said, it may be a good idea to allowing editing torrc via the little box, too. If we decide to do this, editing function should be disabled by default and only be enabled after users checking a checkbox. Otherwise, inexperience/careless users may accidentally change something in the torrc without noticing.
Sadly I speculate most people will be utterly confused if the config
page is shown by default. Thinking they have to do some changes, no idea
what, abort and give up. I fear for usability, best we can do is having
a checkbox for advanced users or a button show config. Even that could
be too much. You tell me.
Here are several potential solutions to that problem:
add a sentence in torrc_page, saying âThe following is for experienced users to have a general view of torrc file. It does not matter if you do not know what this mean, just hit the Next button.â
add a checkbox on the first page, saying â[advanced only] I want to have a look at the torrc file before connecting to the Tor networkâ, and unchecked by defualt.
add a button to show the torrc file.
do nothing about showing users the torrc file.
We may adopt the solution 1 and 2 at the same time.
For solution 3, the tricky thing is where we should place the button. It can be confusing if it appears on every page. But it also does not make sense to appear on one specific page.
Whonix 14 release is at least 1 month if not more away.
How are our chances for torrc.d support in Tor from a Tor version from deb.torproject.org Tor stable stretch repository? Perhaps we have a chance to not need to ship the edit marker approach?
And if we need to ship the edit marker approach we need to plan ahead how to migrate to torrc.d. (Just take the edit marker block and move it to its own file?)
since bridges are used in anon-connection-wizard.torrc, when we use arm to check the connection, tor should connect to one of the bridges, if torrc.d style configuration worked. However, it didnât work.