unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: Vagrant Cascadian <vagrant@debian.org>,
	Mark H Weaver <mhw@netris.org>,
	32674@debbugs.gnu.org
Subject: [bug#32674] [PATCH 0/1] Use gpgv and keybox files for 'guix refresh' & co.
Date: Sun, 16 Sep 2018 23:02:04 +0200	[thread overview]
Message-ID: <87y3c1dulv.fsf@gnu.org> (raw)
In-Reply-To: <20180913162904.GA11458@jasmine.lan> (Leo Famulari's message of "Thu, 13 Sep 2018 12:29:04 -0400")

Hello,

Leo Famulari <leo@famulari.name> skribis:

> On Sun, Sep 09, 2018 at 10:43:35PM +0200, Ludovic Courtès wrote:
>> Hello Guix,
>> 
>> (Cc’ing people with expertise and interest in this…)
>> 
>> This patch changes (guix gnupg) so that it uses keyrings in the “keybox”
>> file format to store and read upstream public keys (instead of using the
>> user’s default keyring), and so that it uses ‘gpgv --keyring’ instead
>> of ‘gpg --verify’.
>> 
>> ‘gpgv’ is specifically designed for use cases like software signature
>> verification against a keyring of “trusted keys” (it’s used by APT and
>> Werner Koch recommends it¹.)  A significant difference compared to
>> ‘gpg --verify’ is that it doesn’t check whether keys are expired or
>> revoked; all that matters is whether the signature is valid and whether
>> the signing key is in the specified keyring.  I think that’s what we
>> want when checking the signature of a tarball or Git commit.
>
> Great, this is a big improvement. It would be awesome if we could get
> similar support in Git (or find another way to authenticate our code).

Yes, that was partly the motivation for this change.

Pushed as b9e1fddfd8c29b2fa6252ef52a75daa14aaabd3e.

Thanks Mike & Leo for your feedback!

Ludo’.

      reply	other threads:[~2018-09-16 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-09 20:43 [bug#32674] [PATCH 0/1] Use gpgv and keybox files for 'guix refresh' & co Ludovic Courtès
2018-09-09 20:46 ` [bug#32674] [PATCH 1/1] gnupg: Use 'gpgv' and keybox files; adjust 'guix refresh' accordingly Ludovic Courtès
2018-09-10  1:55 ` [bug#32674] [PATCH 0/1] Use gpgv and keybox files for 'guix refresh' & co Mike Gerwitz
2018-09-13 16:29 ` Leo Famulari
2018-09-16 21:02   ` Ludovic Courtès [this message]

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=87y3c1dulv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=32674@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=mhw@netris.org \
    --cc=vagrant@debian.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).