Bug #9256

Don't restart Tor after setting the right clock

Added by intrigeri 2015-04-17 09:33:10 . Updated 2019-08-11 18:16:25 .

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

0%

Feature Branch:
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

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.

Subtasks

Related issues

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

History

#1 Updated by intrigeri 2015-04-17 09:34:00

  • Assignee set to anonym

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

#2 Updated by sajolida 2015-09-07 10:41:53

#3 Updated by sajolida 2015-09-22 07:47:37

  • Target version deleted (Sustainability_M1)

#4 Updated by intrigeri 2019-05-18 06:46:33

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

#5 Updated by hefee 2019-05-21 22:31:52

It looks like this is solved together with Bug #16471.

#6 Updated by hefee 2019-05-21 22:33:08

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

#7 Updated by hefee 2019-05-21 22:33:11

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

#8 Updated by intrigeri 2019-08-11 16:58:39

hefee wrote:
> It looks like this is solved together with Bug #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 2019-08-11 17:00:05

  • Assignee deleted (anonym)

#10 Updated by intrigeri 2019-08-11 17:17:11

  • Description updated
  • Assignee set to intrigeri

I’ll try this.

#11 Updated by intrigeri 2019-08-11 18:16:25

  • 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 Bug #16471#note-46, so it does not teach us anything here. Later.