Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.security > #5144

Re: HTTPS needs to be implemented for updating

From datanoise <datanoise@bitjungle.info>
Newsgroups linux.debian.security
Subject Re: HTTPS needs to be implemented for updating
Date 2016-12-18 13:10 +0100
Message-ID <sPIrT-7AW-9@gated-at.bofh.it> (permalink)
References <sPtMd-5Vj-1@gated-at.bofh.it> <sPHvQ-70q-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Christoph Moench-Tegeder :
> ## gwmfms06@unseen.is (gwmfms06@unseen.is):
>
>> What with Let's Encrypt now active, there is no excuse to not move
>> everything to HTTPS for updating.
> 1. Bandwidth. It's fairly easy to proxy/cache HTTP, but HTTPS prevents
>     that (unless you break HTTPS). This not only affects the server
>     side (I have no idea about the amount of "traffic saved" for Debian),
>     but also sites running multiple machines with Debian installed.
>     Setting up a mirror is more work than just running a squid.
> 2. That brings us to: Mirrors. There's quite a bunch of them, and
>     I'm quite sure that some of them (even primary mirrors) are not
>     "Debian Project hardware". That way it's not just "throw a switch
>     and everything is SSL", and it even creates some interesting
>     questions like third parties (those non-Debian mirror admins)
>     having access to debian.org SSL keys.
>
> First point is an inconvenience, second point requires a lot of work
> to resolve.

There could be https mirrors as well as non-https mirrors.

Each individual / company could decide to use a non-https mirror if they 
so prefer.

(Some https mirrors are already available, for example mirrors.kernel.org)

Cheers

Back to linux.debian.security | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


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