Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • B blueprints
  • Project information
    • Project information
    • Activity
    • Members
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
Collapse sidebar
  • tails
  • blueprints
  • Wiki
  • robust_time_syncing

robust_time_syncing · Changes

Page history
Remove 1 level of TOC authored Dec 14, 2021 by sajolida's avatar sajolida
Hide whitespace changes
Inline Side-by-side
robust_time_syncing.md
View page @ 21aed654
......@@ -85,11 +85,8 @@ Some other requirements about this mechanism:
and the time is being sync'ed, both on success and on various kinds
of failures.
Possible solutions
==================
Current plan
------------
============
Meta:
......@@ -115,7 +112,7 @@ tl;dr:
- Else, when the user chooses to hide Tor, ask them fix the time zone and clock manually.
Old plan
--------
========
... when Tor fails to bootstrap for time-related reasons.
......@@ -128,7 +125,7 @@ That's what ChromeOS does when the time is too wrong:
understand why they did what. Still, the resulting code is there:
<https://src.chromium.org/viewvc/chrome?revision=266431&view=revision>
### User story
## User story
When I start Tails
And I log into the Tails desktop with the default options
......@@ -138,9 +135,9 @@ That's what ChromeOS does when the time is too wrong:
And then, Tails Clock displays the current time with the chosen timezone
And Tor bootstrap is attempted again
### Roadmap
## Roadmap
#### First iteration
### First iteration
Relevant tickets: tails/tails#10819, tails/tails#6284,
tails/tails#12094.
......@@ -177,7 +174,7 @@ tails/tails#12094.
timezone when they set it from Tails Clock or from the
aforementioned GUI.
#### Second iteration
### Second iteration
We stop using htpdate to *set* the system clock, but we keep it around
as a way to *detect* a replayed Tor consensus: if the time delta
......@@ -191,7 +188,7 @@ And then, perhaps htpdate could be configured to query fewer servers,
because we maybe don't need to trust the info we get from htpdate as
much once we're there.
#### Integration with the new Greeter
### Integration with the new Greeter
We need to give the user will have the opportunity to choose their
preferred timezone in the Greeter (tails/tails#11645). And then,
......@@ -212,7 +209,7 @@ Tor has failed to bootstrap for time-related reasons.
And Tor has greater chances to bootstrap successfully on first try
Extend Tor some how
-------------------
===================
E.g.:
......
Clone repository
  • Home
  • Monthly reports
  • Sandbox