From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 27437@debbugs.gnu.org
Subject: bug#27437: Source downloader accepts X.509 certificate for incorrect domain
Date: Thu, 22 Jun 2017 21:12:27 +0200 [thread overview]
Message-ID: <87wp83rg4k.fsf@gnu.org> (raw)
In-Reply-To: <20170622161108.GA15580@jasmine.lan> (Leo Famulari's message of "Thu, 22 Jun 2017 12:11:08 -0400")
Leo Famulari <leo@famulari.name> skribis:
> 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 :/
Agreed.
That said, if we look at our updaters:
--8<---------------cut here---------------start------------->8---
$ guix refresh --list-updaters
Available updaters:
- cpan: Updater for CPAN packages (9.2% coverage)
- cran: Updater for CRAN packages (4.0% coverage)
- bioconductor: Updater for Bioconductor packages (1.2% coverage)
- crates: Updater for crates.io packages (.0% coverage)
- elpa: Updater for ELPA packages (.3% coverage)
- gem: Updater for RubyGem packages (2.5% coverage)
- github: Updater for GitHub packages (10.5% coverage)
- hackage: Updater for Hackage packages (5.2% coverage)
- pypi: Updater for PyPI packages (17.6% coverage)
- stackage: Updater for Stackage LTS packages (5.2% coverage)
- kernel.org: Updater for packages hosted on kernel.org (.5% coverage)
- gnome: Updater for GNOME packages (2.9% coverage)
- xorg: Updater for X.org packages (3.2% coverage)
- gnu: Updater for GNU packages (5.6% coverage)
- kde: Updater for KDE packages (1.3% coverage)
69.0% of the packages are covered by these updaters.
--8<---------------cut here---------------end--------------->8---
I think only GNU and kernel.org provide signatures, which represents 6%
of our packages. Of the 30% that do not have an updater, surely some
have digital signatures, but we’re probably still below 10%. The
situation is bad in general…
Ludo’.
next prev parent reply other threads:[~2017-06-22 19:13 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
2017-06-22 19:12 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wp83rg4k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27437@debbugs.gnu.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.