Re: When should we https our mirrors?
]] Paul Tagliamonte
> So, when are we going to push this? If not now, what criteria need to
> be met? Why can't we https-ify the default CDN mirror today?
The usual crypto answer: because key handling is hard.
Doing this for the per-country mirrors means that repointing mirrors
becomes a lot harder than it currently is, and this is something we do
on a daily basis. We'd need a solution for deploying the TLS cert for,
say, ftp.de.d.o to ftp.se.d.o (or ftp.d.o) if ftp.d.o is down for
Doing this for deb.d.o would mean we need to get certs on both Fastly
and Cloudfront deployed, which is, frankly, a more realistic proposition
than jury-rigging something on the per-country mirrors.
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are