Tails

#2 Updated by anonym 2017-07-04 11:11:20

• Status changed from Confirmed to In Progress
• % Done changed from 0 to 30

(Instead of bumping the torproject snapshot serial (due to Bug #13413)) I uploaded these packages to stable’s APT suite:

tor_0.3.0.9-1~d90.stretch+1_amd64.deb
tor-dbg_0.3.0.9-1~d90.stretch+1_amd64.deb
tor-geoipdb_0.3.0.9-1~d90.stretch+1_all.deb

I claim that these are the ones from deb.torproject.org. :)

#3 Updated by anonym 2017-07-04 11:46:45

• related to Bug #13416: Restore APT pinning of deb.tp.o added

#4 Updated by anonym 2017-07-04 11:52:21

• Status changed from In Progress to Fix committed
• Assignee changed from anonym to intrigeri
• % Done changed from 30 to 100
• QA Check set to Ready for QA

So I also had to commit 0e8ef1fe71bae0f48e8e65186a656e1e8169e7bc (due to Bug #13413, which incorrectly puts the (higher version) buster packages in our stretch snapshot), and its reversal is tracked as Bug #13416.

intrigeri, can you please make sure I didn’t upload any backdoor’s in the above .deb:s? Just unassign yourself, in either case.

#5 Updated by anonym 2017-07-04 15:52:00

• Status changed from Fix committed to In Progress

Applied in changeset commit:0e8ef1fe71bae0f48e8e65186a656e1e8169e7bc.

#6 Updated by intrigeri 2017-07-05 05:51:56

• blocks Feature #13234: Core work 2017Q3: Foundations Team added

#7 Updated by intrigeri 2017-07-05 08:31:24

• Status changed from In Progress to Fix committed
• Assignee deleted (intrigeri)
• QA Check changed from Ready for QA to Pass

anonym wrote:
> intrigeri, can you please make sure I didn’t upload any backdoor’s in the above .deb:s? Just unassign yourself, in either case.

I don’t see why I should check this, while we’re not checking our custom packages.

#8 Updated by intrigeri 2017-07-05 19:03:52

• Status changed from Fix committed to Resolved