Feature #8194
Have APT directly use the Tor SOCKS proxy
50%
Description
See parent ticket for the rationale and early work on this.
Subtasks
Related issues
Related to Tails - |
Resolved | 2014-11-03 | |
Blocks Tails - |
Resolved |
History
#1 Updated by intrigeri 2014-11-02 00:37:27
Failed to backport apt-transport-tor for Wheezy, asked the maintainer.
Someone should retry the shim idea, then, as documented on the parent ticket. I think that our build system now supports some APT breakage after hooks have been run, and we already cause such breakage with config/chroot_local-hooks/99-zzz_runtime_apt_proxy
I think, so maybe we could as well do an elaborate s,http://,tor://,
in APT sources.
#2 Updated by intrigeri 2014-11-03 10:52:50
- Status changed from Confirmed to In Progress
- Target version changed from Hardening_M1 to Tails_1.3
- % Done changed from 0 to 50
- QA Check set to Ready for QA
- Feature Branch set to feature/8194-APT-socks
The shim works fine. Passes the apt
, build
and firewall_leaks
automatic test suite features. Retargetting to 1.3, then :)
We should try to replace this trick with proper use of apt-transport-tor
once we are based on Jessie.
#3 Updated by intrigeri 2014-11-03 10:56:38
- related to
Feature #8198: Replace tor+http shim with apt-transport-tor added
#4 Updated by intrigeri 2014-11-03 11:13:34
Incidentally, this branch fixes the APT errors we’ve been seeing in the build log since the migration to Wheezy.
#5 Updated by intrigeri 2014-11-08 09:19:07
- blocks
Feature #5307: Fix the Wheezy build in a nicer way added
#6 Updated by alant 2014-12-23 16:11:44
- Status changed from In Progress to Fix committed
- QA Check changed from Ready for QA to Pass
Merged thanks!
#7 Updated by BitingBird 2015-02-24 22:49:42
- Status changed from Fix committed to Resolved