-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Mar 06, 2016 at 08:13:49PM +, Ben Hutchings wrote:
> On Sun, 2016-03-06 at 19:19 +, Bas Wijnen wrote:
> > On Sun, Mar 06, 2016 at 07:35:57PM +0100, Jakub Wilk wrote:
> > >
> > > So, what we're going to do about it? I see the following
On Sun, 2016-03-06 at 19:19 +, Bas Wijnen wrote:
> On Sun, Mar 06, 2016 at 07:35:57PM +0100, Jakub Wilk wrote:
> >
> > So, what we're going to do about it? I see the following options:
> >
> > B) Fix the spec to allow the HTTPS URL; fix the HTTP-only consumers.
> That. Https is good for our
Bas Wijnen writes:
> On Sun, Mar 06, 2016 at 07:35:57PM +0100, Jakub Wilk wrote:
>> So, what we're going to do about it? I see the following options:
>> B) Fix the spec to allow the HTTPS URL; fix the HTTP-only consumers.
> That. Https is good for our users. Even if the effect of this change
Le dimanche 6 mars 2016, 19:19:35 Bas Wijnen a écrit :
> That. Https is good for our users. Even if the effect of this change is very
> minor, we should show them that it should be the default everywhere.
>
Having https://incoming.debian.org/ would be nice too.
Alexandre
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Mar 06, 2016 at 07:35:57PM +0100, Jakub Wilk wrote:
> So, what we're going to do about it? I see the following options:
>
> B) Fix the spec to allow the HTTPS URL; fix the HTTP-only consumers.
That. Https is good for our users. Even if the
On Sun, Mar 06, 2016 at 07:35:57PM +0100, Jakub Wilk wrote:
> The machine-readable debian/copyright file specification says that
> the Format field should contain:
>
> http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>
> These days www.debian.org supports HTTPS+HSTS (thanks, DSA!
The machine-readable debian/copyright file specification says that the
Format field should contain:
http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
These days www.debian.org supports HTTPS+HSTS (thanks, DSA!). Apparently
this prompted some people to replace "http" with "https
7 matches
Mail list logo