Redesign the network configuration and startup
Building up on our reflections on the Greeter, the Tor progress bar (#7437), the persistent Tor configuration (#5462), the time synchronization (#5774), the whole process of deciding how to connect to the network and based on that getting a working Tor should be redesigned as a whole.
While working on this we should be careful about the different aspects mentioned above, their technical feasibility, and how we could propose an incremental process.
#17 Updated by intrigeri over 2 years ago
- Assignee deleted (
- QA Check deleted (
@sajolida: is this still something we should do?
Yes, it was even a strong candidate for our roadmap :)
I'm unable to figure out how much of this proposal was implemented in the greeter already.
Nothing at all.
#18 Updated by u over 2 years ago
Ok, I understand better now.
So I am closing #7440 and #7438 and #7347: Design & implement a progress indicator between clock synchronization and Tor being ready. The main information is on #7437: this was the outcome of our first user testing session. This should be reviewed with the outcome of #11245 and implemented in the new design.
#20 Updated by iry almost 2 years ago
- We will still keep the Tails greeter but move the network connection and MAC spoof part into "network connection wizard".
- There are still many problem need to be sorted out before implementation:
- anon-connection-wizard is PyQt5 based while Tails prefers GTK. (The PyQt applications are already included in Tails though).
- The webkit which may used in network connection wizard to replace some of the use case of insecure browser(e.g airport WiFi login) sometimes needs to be alive all the time (otherwise the airport WiFi may disconnect).
- The network connection wizard is more of a future goal.
#22 Updated by sajolida about 1 year ago
"Can't connect to Tor" has been reported as a frequent issue on the Cybelle's report from July, see https://mailman.boum.org/pipermail/tails-ux/2018-August/003567.html.