all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gerwitz <mtg@gnu.org>
Cc: 27437@debbugs.gnu.org
Subject: bug#27437: Source downloader accepts X.509 certificate for incorrect domain
Date: Fri, 23 Jun 2017 11:31:40 +0200	[thread overview]
Message-ID: <87podvaw3n.fsf@gnu.org> (raw)
In-Reply-To: <87y3sj7cqx.fsf@gnu.org> (Mike Gerwitz's message of "Thu, 22 Jun 2017 20:45:42 -0400")

Mike Gerwitz <mtg@gnu.org> skribis:

> On Thu, Jun 22, 2017 at 21:12:27 +0200, Ludovic Courtès wrote:
>> 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…
>
> What about signed tags/commits?

They’re becoming more widespread, especially now that GitHub’s UI can
make sense of them.  Nevertheless, I don’t think it changes the ratio
much if we look at the whole package set that we have.

Ludo’.

  reply	other threads:[~2017-06-23  9:32 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
2017-06-23  0:45         ` Mike Gerwitz
2017-06-23  9:31           ` Ludovic Courtès [this message]
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=87podvaw3n.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=27437@debbugs.gnu.org \
    --cc=mtg@gnu.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 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.