Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.security > #5147
| From | Hans-Christoph Steiner <hans@at.or.at> |
|---|---|
| Newsgroups | linux.debian.security |
| Subject | Re: HTTPS needs to be implemented for updating |
| Date | 2016-12-19 12:00 +0100 |
| Message-ID | <sQ3PH-6CU-5@gated-at.bofh.it> (permalink) |
| References | <sPtMd-5Vj-1@gated-at.bofh.it> <sPHvQ-70q-9@gated-at.bofh.it> <sPRbP-7ay-7@gated-at.bofh.it> |
| Organization | @||@ |
Peter Lawler: > > > On 18/12/16 22:03, Christoph Moench-Tegeder wrote: >> second point requires a lot of work >> to resolve. >> >> Regards, >> Christoph >> > > Monday morning yet-to-be-caffienated thoughts... > > I'm going to ignore the 'inconvenience' because I think in this case > that's a specious argument. > > I acknowledge there's a bucketload of work to implement this. Just gets > me to thinking, staging a switch over may be better. eg, a new apt > config for https as either 'required' 'desired' and 'off'. This reduces > the initial workload. Start with the default 'off', then at some future > release move to 'desired' then 'required'. > > Further, I suggest perhaps an automated survey of the major mirrors to > find which ones already support https may be in order. Perhaps the > resultant data could be used by the apt-transport-https package for now, > as well as deciding when the above mentioned switch over might occur. > > As I say, decaffienated Monday morning thoughts. > Here's a script I wrote to do just that, find all Debian mirrors that support HTTPS: https://gist.github.com/eighthave/7285154 .hc
Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
HTTPS needs to be implemented for updating gwmfms06@unseen.is - 2016-12-17 21:30 +0100
Re: HTTPS needs to be implemented for updating Christoph Moench-Tegeder <cmt@burggraben.net> - 2016-12-18 12:10 +0100
Re: HTTPS needs to be implemented for updating datanoise <datanoise@bitjungle.info> - 2016-12-18 13:10 +0100
Re: HTTPS needs to be implemented for updating Casper Thomsen <ct@clearhaus.com> - 2016-12-19 09:20 +0100
Re: HTTPS needs to be implemented for updating Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2016-12-20 23:20 +0100
Re: HTTPS needs to be implemented for updating Joerg Jaspert <joerg@debian.org> - 2016-12-21 09:40 +0100
Re: HTTPS needs to be implemented for updating Marc Haber <mh+debian-security@zugschlus.de> - 2016-12-21 10:00 +0100
Re: HTTPS needs to be implemented for updating Christoph Biedl <debian.axhn@manchmal.in-ulm.de> - 2016-12-21 10:10 +0100
Re: HTTPS needs to be implemented for updating Peter Lawler <relwalretep@gmail.com> - 2016-12-18 22:30 +0100
Re: HTTPS needs to be implemented for updating Hans-Christoph Steiner <hans@at.or.at> - 2016-12-19 12:00 +0100
Re: HTTPS needs to be implemented for updating Hans-Christoph Steiner <hans@at.or.at> - 2016-12-20 10:50 +0100
Re: HTTPS needs to be implemented for updating Sven Hartge <sven@svenhartge.de> - 2016-12-20 18:20 +0100
Re: HTTPS needs to be implemented for updating Martin Zobel-Helas <zobel@debian.org> - 2017-03-03 11:30 +0100
csiph-web