Feature #7342

Upgrade to Tor 0.2.4.22

Added by intrigeri 2014-05-30 02:07:11 . Updated 2014-07-22 23:12:39 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_1.1
Start date:
2014-05-30
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

Subtasks

History

#1 Updated by intrigeri 2014-05-30 02:08:36

  • Status changed from Confirmed to In Progress
  • Assignee set to anonym
  • % Done changed from 0 to 10

Assuming feature/tor-0.2.4.22 was started by anonym, assigning to him for now. Note that the 1010 pin priority feels right to test, but wrong to merge: instead, this branch should delete our custom 0.2.4.21 patched tor.

#2 Updated by anonym 2014-06-06 07:34:17

intrigeri wrote:
> Assuming feature/tor-0.2.4.22 was started by anonym, assigning to him for now. Note that the 1010 pin priority feels right to test, but wrong to merge: instead, this branch should delete our custom 0.2.4.21 patched tor.

I pushed that branch to test the (at the time) current state of Tails with Tor 0.2.4.22. When all looked good, I just deleted our patched 0.2.4.21 from the devel APT repo in time for the 1.1~beta1 freeze. I thought this was ok without further process (like a review’n’merge) since we’d silently have gotten the 0.2.4.21 —> 0.2.4.22 update if we didn’t have our custom Tor package in our APT suite, just like any other security update.

IMHO that branch should be deleted and this ticket should be either rejected or set as fix committed.

#3 Updated by intrigeri 2014-06-06 08:18:32

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • % Done changed from 10 to 100
  • Feature Branch deleted (feature/tor-0.2.4.22)

#4 Updated by BitingBird 2014-07-22 23:12:39

  • Status changed from Fix committed to Resolved