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
Update robust_time_syncing authored Nov 30, 2021 by intrigeri's avatar intrigeri
Hide whitespace changes
Inline Side-by-side
robust_time_syncing.md
View page @ 246a92f6
......@@ -34,14 +34,18 @@ the time is outside the current Tor network consensus'
the `valid-after` and `valid-until` fields). When Tor fails to
bootstrap, Tails is effectively useless for networking.
It should be noted that the clock just has to be off by a few hours
It should be noted that when using obfs4 bridges, the clock just has to be off by a few hours
for Tor to become completely unable to bootstrap, and that's not very
uncommon. Certain OSes (including Windows up to Windows 8 at least)
set the BIOS clock to the local time, and since Tails uses UTC (and
assumes the BIOS clock is UTC), this becomes a problem for every user
but those living in the GMT+0/UTC timezone. Hence this is a very
who needs obfs4 bridges, and whose clock is set to system time,
unless they live in the GMT+0/UTC timezone. Hence this is a very
serious problem.
When connecting to Tor directly or using regular bridges,
the clock can be off by a few hours without causing bootstrapping trouble.
What we want
------------
......
Clone repository
  • Home
  • Monthly reports
  • Sandbox