Feature #10491

Redesign the network configuration and startup

Added by sajolida 2015-11-06 03:50:42 . Updated 2018-11-21 16:01:55 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Target version:
2020
Start date:
2014-06-22
Due date:
% Done:

50%

Feature Branch:
Type of work:
Research
Blueprint:

https://tails.boum.org/blueprint/network_connection

Starter:
Affected tool:
Deliverable for:

Description

Building up on our reflections on the Greeter, the Tor progress bar (Feature #7437), the persistent Tor configuration (Feature #5462), the time synchronization (Feature #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.

Files

2015.10.02.jpg (576988 B) SpencerOne, 2016-02-16 17:40:10
2015.12.04.png (112313 B) SpencerOne, 2016-02-16 17:40:20

Subtasks

Feature #7438: Design a progress indicator until Tor is ready Duplicate

0
Feature #7439: Decide whether to remove the "clock synchronization" notification Confirmed

0
Feature #8061: Customize "Proxy is refusing connections" error messages in Tor Browser and remove the "Tor is not ready" popup Confirmed

0
Feature #11245: Process feedback from IFF UX session Resolved

0

Related issues

Related to Tails - Feature #5461: Persistence preset: Tor configuration Confirmed
Related to Tails - Feature #5785: Detect captive portals Confirmed 2014-09-26
Related to Tails - Bug #10100: Enable Unsafe browser + Clearnet user via Greeter Rejected 2015-08-26
Related to Tails - Feature #11293: Check if/how we should use NetworkManager's new MAC address spoofing capabilities Confirmed 2016-03-31
Related to Tails - Bug #15635: The Unsafe Browser allows to retrieve the public IP address by a compromised amnesia user with no user interaction Confirmed 2018-06-04
Related to Tails - Feature #5555: Torbrowser patches vs. Unsafe browser Confirmed
Related to Tails - Feature #5412: Improve fingerprint of the Unsafe Browser Rejected
Has duplicate Tails - Bug #12198: UI for Tor config doesn't show up until there's net connection Duplicate 2017-01-31
Has duplicate Tails - Feature #15861: Revamp the network connection process Duplicate 2018-08-30
Blocks Tails - Feature #15859: Remove Unsafe Browser Confirmed 2018-08-30

History

#1 Updated by sajolida 2015-11-06 03:51:10

  • related to Feature #5461: Persistence preset: Tor configuration added

#2 Updated by sajolida 2015-11-06 03:51:17

  • related to Feature #7437: Consider adding a progress indicator while establishing a connection to Tor added

#3 Updated by sajolida 2015-11-06 05:20:15

  • File <del>missing: 20151002-lunar.jpg</del> added
  • File <del>missing: 20151005-spencer.png</del> added

Adding two images from Lunar and Spencer.

#4 Updated by sajolida 2015-11-06 05:29:22

#5 Updated by sajolida 2015-12-03 10:14:37

  • related to Bug #10100: Enable Unsafe browser + Clearnet user via Greeter added

#6 Updated by SpencerOne 2015-12-03 10:22:41

  • Description updated

#7 Updated by SpencerOne 2015-12-09 11:02:11

  • File deleted (20151005-spencer.png)

#8 Updated by SpencerOne 2015-12-09 11:03:08

  • File <del>missing: Startup.0.1.png</del> added

#9 Updated by SpencerOne 2016-02-16 17:29:01

  • File deleted (20151204.png)

#10 Updated by SpencerOne 2016-02-16 17:37:44

  • File deleted (20151002-lunar.jpg)

#11 Updated by SpencerOne 2016-02-16 17:40:51

Pics keep breaking.

Fixed (:

#12 Updated by intrigeri 2016-08-27 10:12:54

  • Target version deleted (2016)

#13 Updated by intrigeri 2017-01-02 19:57:20

  • related to Feature #11293: Check if/how we should use NetworkManager's new MAC address spoofing capabilities added

#14 Updated by intrigeri 2017-02-07 16:50:29

  • has duplicate Bug #12198: UI for Tor config doesn't show up until there's net connection added

#15 Updated by Anonymous 2017-06-30 08:53:09

  • Assignee set to sajolida
  • QA Check set to Info Needed

@sajolida: is this still something we should do? I’m unable to figure out how much of this proposal was implemented in the greeter already. You can unassign yourself after answering :)

#16 Updated by Anonymous 2017-06-30 09:17:26

  • related to deleted (Feature #7437: Consider adding a progress indicator while establishing a connection to Tor)

#17 Updated by intrigeri 2017-06-30 09:49:39

  • Assignee deleted (sajolida)
  • QA Check deleted (Info Needed)

u wrote:
> @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 Anonymous 2017-06-30 10:04:26

Ok, I understand better now.

So I am closing Feature #7440 and Feature #7438 and #7347: Design & implement a progress indicator between clock synchronization and Tor being ready. The main information is on Feature #7437: this was the outcome of our first user testing session. This should be reviewed with the outcome of Feature #11245 and implemented in the new design.

#19 Updated by sajolida 2017-07-10 19:16:16

That’s brave ticket triaging but I fully agree. Thanks for cleaning things up so well!

#20 Updated by iry 2018-01-12 16:27:19

Anonym and I had a discussion on the proposed “network connection wizard”. My understanding is summarized as follows and please correct me if there is anything wrong:

  1. We will still keep the Tails greeter but move the network connection and MAC spoof part into “network connection wizard”.
  2. The network connection wizard is supposed to be a unified application at least in terms of users feeling.
  3. There are still many problem need to be sorted out before implementation:
    1. anon-connection-wizard is PyQt5 based while Tails prefers GTK. (The PyQt applications are already included in Tails though).
    2. 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).
  4. The network connection wizard is more of a future goal.

#21 Updated by intrigeri 2018-06-10 17:06:24

  • related to Bug #15635: The Unsafe Browser allows to retrieve the public IP address by a compromised amnesia user with no user interaction added

#22 Updated by sajolida 2018-08-17 06:45:39

“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.

#23 Updated by intrigeri 2018-08-19 11:52:18

  • related to Feature #5555: Torbrowser patches vs. Unsafe browser added

#24 Updated by intrigeri 2018-08-19 11:52:39

  • related to Feature #5412: Improve fingerprint of the Unsafe Browser added

#25 Updated by nodens 2018-08-30 14:16:37

  • has duplicate Feature #15861: Revamp the network connection process added

#26 Updated by nodens 2018-08-30 14:17:10

#27 Updated by Anonymous 2018-09-02 14:18:28

  • Target version set to 2019

#28 Updated by intrigeri 2018-10-11 09:29:54

  • blocked by #15903 added

#29 Updated by intrigeri 2018-10-11 09:30:10

  • Target version changed from 2019 to 2020