https (SSL / TLS) by default broke apt-cacher-ng apt package caching during build


E: Failed to fetch https://deb.debian.org/debian-security/dists/stretch/updates/main/binary-amd64/Packages Received HTTP code 403 from proxy after CONNECT

To be expected:


Perhaps the "tell-me-what-you-need method" mentioned there would help.

This makes also enabling https (SSL / TLS) in anon-apt-soures-list (/etc/apt/sources.list.d/debian.list) difficult. "tell-me-what-you-need method" is hard to add in /etc/apt/sources.list.d/debian.list but it is being used during build of Whonix.


maybe if you fill that as a bug to debian , might consider to look/change something which will help the build.

Not a Debian bug. Known and documented limitation. An (apt package)
caching proxy can’t cache end-to-end encrypted SSL’ed connections by
design. Not easy without hacks.

many distros that i know use ssl by default for their repos like parrotsec, trisquel…etc so maybe check their code or how they implemented that and see if it can fit to our distro.

[Imprint] [Privacy Policy] [Cookie Policy] [Terms of Use] [E-Sign Consent] [DMCA] [Investors] [Priority Support] [Professional Support]