Project

General

Profile

Bug #9256

Don't restart Tor after setting the right clock

Added by intrigeri over 4 years ago. Updated about 1 month ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Time synchronization
Target version:
-
Start date:
04/17/2015
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:

Description

IIRC we're restarting Tor after setting the right clock, because it's not able to recover when it was started with a skewed clock. There's been progress upstream about that. We should check if we can get rid of some 20-time.sh ugliness thanks to these changes.


Related issues

Related to Tails - Feature #5774: Robust time syncing In Progress 05/17/2015
Blocked by Tails - Bug #16471: Drop time synchronization hacks that tor 0.3.5 and 0.4.x made obsolete In Progress 02/17/2019

History

#1 Updated by intrigeri over 4 years ago

  • Assignee set to anonym

anonym, is this something that you would happily look into while "procrastinating", perhaps?

#2 Updated by sajolida about 4 years ago

#3 Updated by sajolida about 4 years ago

  • Target version deleted (Sustainability_M1)

#4 Updated by intrigeri 4 months ago

  • Related to Bug #16471: Drop time synchronization hacks that tor 0.3.5 and 0.4.x made obsolete added

#5 Updated by hefee 4 months ago

It looks like this is solved together with #16471.

#6 Updated by hefee 4 months ago

  • Related to deleted (Bug #16471: Drop time synchronization hacks that tor 0.3.5 and 0.4.x made obsolete)

#7 Updated by hefee 4 months ago

  • Blocked by Bug #16471: Drop time synchronization hacks that tor 0.3.5 and 0.4.x made obsolete added

#8 Updated by intrigeri about 1 month ago

hefee wrote:

It looks like this is solved together with #16471.

Not quite, unfortunately: more recent progress suggests we'll still have to set the clock from the Tor consensus in some cases.

#9 Updated by intrigeri about 1 month ago

  • Assignee deleted (anonym)

#10 Updated by intrigeri about 1 month ago

  • Description updated (diff)
  • Assignee set to intrigeri

I'll try this.

#11 Updated by intrigeri about 1 month ago

  • Assignee deleted (intrigeri)

"Scenario: Clock is one day in the future in bridge mode" fails, but that's probably the problem I've mentioned on #16471#note-46, so it does not teach us anything here. Later.

Also available in: Atom PDF