... | @@ -105,14 +105,16 @@ UX design: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/network_connec |
... | @@ -105,14 +105,16 @@ UX design: https://gitlab.tails.boum.org/tails/blueprints/-/wikis/network_connec |
|
|
|
|
|
tl;dr:
|
|
tl;dr:
|
|
|
|
|
|
- If the user chooses autoconfig, then do unsafe NTP so Tor can bootstrap.
|
|
- If the user chooses autoconfig, then:
|
|
We'll decide on tails/tails#18230 if and how we can do that.
|
|
|
|
Then, once Tor has bootstrapped, do a safer time sync.
|
|
1. We set the clock from the network without using Tor, so Tor can bootstrap. We've decided how we can do that: https://tails.boum.org/contribute/design/Tor_enforcement/#non-tor-traffic.
|
|
|
|
2. We let Tor bootstrap.
|
|
|
|
3. Once Tor has bootstrapped, do a safer time sync with htpdate.
|
|
|
|
|
|
- Else, when the user chooses to hide Tor, ask them fix the time zone and clock manually.
|
|
- Else, when the user chooses to hide Tor, ask them fix the time zone and clock manually.
|
|
|
|
|
|
Ask the user what time it is
|
|
Old plan
|
|
----------------------------
|
|
--------
|
|
|
|
|
|
... when Tor fails to bootstrap for time-related reasons.
|
|
... when Tor fails to bootstrap for time-related reasons.
|
|
|
|
|
... | | ... | |