Drop time synchronization hacks that tor 0.3.5 and 0.4.x made obsolete
Originally created by @hefee on #16471 (Redmine)
And here’s a list of little-t-tor changes that might be relevant, e.g. they may break or time sync hacks or instead make some of them obsolete:
- https://trac.torproject.org/projects/tor/ticket/28591
- https://trac.torproject.org/projects/tor/ticket/24661
- https://trac.torproject.org/projects/tor/ticket/23605
- https://trac.torproject.org/projects/tor/ticket/27691
Some of them were fixed in 0.3.5, some will be in 0.4.x but might be backported to 0.3.5 when we come back to this ticket. As part of this ticket, I expect we will:
- look for breakage and fix it (subtasks of this ticket + report to Tor Network Team if the problem is on their side)
- look for changes that make our code useless but not harmful and file new FT tickets for that (not blockers to close this ticket)
- if it looks like 0.4.x will make a bigger difference, file a ticket about upgrading to 0.4.x and explain your findings there, so we don’t do all the exact same work again once we’re there
Feature Branch: bugfix/16471-drop-time-synchronization-hacks+force-all-tests, https://salsa.debian.org/tails-team/tails/merge_requests/21
Attachments
Related issues
- Related to #16348 (closed)
-
Blocked by #16687 (closed) - Blocks #9256 (closed)
-
Blocked by #16792 (closed)
Edited by hefee