Feature #5424
Think about tordate htpdate changes
Start date:
Due date:
% Done:
0%
Description
First, think how the new tordate + torified htpdate implementation changes why/how this todo item should be implemented.
Subtasks
Related issues
Related to Tails - Feature #5774: Robust time syncing | In Progress | 2015-05-17 | |
Related to Tails - Feature #6112: Safer tordate parameters | Confirmed | ||
Related to Tails - Feature #5773: Revisit network fingerprinting design wrt. NTP | Confirmed | ||
Blocks Tails - |
Rejected |
History
#1 Updated by Tails 2013-07-18 10:34:57
- Parent task set to
Feature #5366
#2 Updated by BitingBird 2014-06-09 10:28:01
- Subject changed from think about tordate htpdate changes to Think about tordate htpdate changes
- Description updated
- Starter set to No
#3 Updated by BitingBird 2015-01-04 03:13:25
- related to Feature #5774: Robust time syncing added
#4 Updated by BitingBird 2015-01-04 03:13:43
- related to Feature #6112: Safer tordate parameters added
#5 Updated by BitingBird 2015-01-04 03:13:59
- related to Feature #5773: Revisit network fingerprinting design wrt. NTP added
#6 Updated by BitingBird 2015-01-04 03:15:12
There seems to be quite a few tickets open about this time sync question, I linked them but maybe there are some duplicates. Since I’m not sure, I let someone with more knowledge sort it out, now that they are highlighted :)
#7 Updated by intrigeri 2015-01-08 09:57:41
- Category set to Time synchronization
#8 Updated by bertagaz 2015-04-09 11:22:05
- blocks
Feature #5613: Document time sync failure added
#9 Updated by intrigeri 2019-03-08 16:43:20
- Status changed from Confirmed to Rejected
Let’s do Feature #5774 instead.