From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: 27437@debbugs.gnu.org
Subject: bug#27437: Source downloader accepts X.509 certificate for incorrect domain
Date: Thu, 22 Jun 2017 12:11:08 -0400 [thread overview]
Message-ID: <20170622161108.GA15580@jasmine.lan> (raw)
In-Reply-To: <87injohwac.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Thu, Jun 22, 2017 at 11:33:31AM -0400, Mark H Weaver wrote:
> ludo@gnu.org (Ludovic Courtès) writes:
> > IOW, since we’re checking the integrity of the tarball anyway, and we
> > assume developers checked its authenticity when writing the recipe, then
> > who cares whether downloads.xiph.org has a valid certificate?
> >
> > Conversely, ‘guix download’ always checks certificates by default.
> >
> > Does it make sense?
>
> Yes, and I agree with this behavior. However, it should be noted that
> this will reduce the security of a bad practice that I suspect is
> sometimes used by people when updating packages, namely to update the
> version number, try building it, and then copy the hash from the error
> message to the package.
Yeah, that's a bad habit and I warn people against it whenever it comes
up :/
> FWIW, I always check digital signatures when they're available, and I
> hope that others will as well, but in practice we are putting our faith
> in a large number of contributors, some of whom might not be so careful.
>
> Also, sadly, many packages are distributed without digital signatures at
> all. One glaring example is NSS.
Do we have any contacts at Mozilla we can talk to about this? I imagine
it's a long shot, with many bureaucratic hurdles, but it's worth asking
for.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-22 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 6:17 bug#27437: Source downloader accepts X.509 certificate for incorrect domain Leo Famulari
2017-06-21 10:50 ` Ludovic Courtès
2017-06-22 4:09 ` Leo Famulari
2017-06-22 7:57 ` Ludovic Courtès
2017-06-22 16:16 ` Leo Famulari
2017-06-22 15:33 ` Mark H Weaver
2017-06-22 16:11 ` Leo Famulari [this message]
2017-06-22 19:12 ` Ludovic Courtès
2017-06-23 0:45 ` Mike Gerwitz
2017-06-23 9:31 ` Ludovic Courtès
2017-06-22 21:30 ` ng0
2017-06-22 21:45 ` Ricardo Wurmus
2017-06-22 22:32 ` Marius Bakke
2017-06-23 3:24 ` Leo Famulari
2017-06-23 7:29 ` Ricardo Wurmus
2017-07-27 12:29 ` Ludovic Courtès
2017-07-27 19:34 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170622161108.GA15580@jasmine.lan \
--to=leo@famulari.name \
--cc=27437@debbugs.gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).