Feature #6112

Safer tordate parameters

Added by Tails 2013-07-18 07:51:08 . Updated 2015-05-18 14:44:18 .

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

0%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

As discussed on tails-dev (4F2FE29F.8040101@lavabit.com, "if we want a long, stable Tor session with a time only handled by tordate (like when htpdate fails), then the only really safe thing to do is to always, no matter what, set the time to fresh-until", which effectively removes "good enough time" check.

  1. implement this
  2. merge into experimental
  3. test in extreme conditions
  4. 4F2FE29F.8040101@lavabit.com also has ideas to improve Tor in these situations, that should be forwarded upstream.

Subtasks

Related issues

Related to Tails - Feature #5774: Robust time syncing In Progress 2015-05-17
Related to Tails - Feature #5424: Think about tordate htpdate changes Rejected

History

#1 Updated by BitingBird 2014-06-09 11:26:40

  • Subject changed from safer tordate parameters to Safer tordate parameters
  • Description updated
  • Starter set to No

#2 Updated by BitingBird 2015-01-02 19:48:24

  • Category set to Tor configuration

#3 Updated by BitingBird 2015-01-02 19:51:45

#4 Updated by intrigeri 2015-01-03 11:12:46

  • Category deleted (Tor configuration)

#5 Updated by BitingBird 2015-01-04 03:13:43

  • related to Feature #5424: Think about tordate htpdate changes added

#6 Updated by BitingBird 2015-01-08 03:24:52

  • Category set to Tor configuration

#7 Updated by intrigeri 2015-01-08 09:54:24

  • Category deleted (Tor configuration)

#8 Updated by intrigeri 2015-01-08 09:55:19

  • Category set to Time synchronization

#9 Updated by intrigeri 2015-05-18 14:44:18

Note that the proposed new design (Feature #5774 + blueprint) for time sync’ will obsolete this ticket.