Project

General

Profile

Feature #6112

Safer tordate parameters

Added by Tails about 6 years ago. Updated about 4 years ago.

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

0%

Feature Branch:
Type of work:
Code
Blueprint:
Starter:
No
Affected tool:

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.

Related issues

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

History

#1 Updated by BitingBird about 5 years ago

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

#2 Updated by BitingBird over 4 years ago

  • Category set to Tor configuration

#3 Updated by BitingBird over 4 years ago

#4 Updated by intrigeri over 4 years ago

  • Category deleted (Tor configuration)

#5 Updated by BitingBird over 4 years ago

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

#6 Updated by BitingBird over 4 years ago

  • Category set to Tor configuration

#7 Updated by intrigeri over 4 years ago

  • Category deleted (Tor configuration)

#8 Updated by intrigeri over 4 years ago

  • Category set to Time synchronization

#9 Updated by intrigeri about 4 years ago

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

Also available in: Atom PDF