From: Maxime Devos <maximedevos@telenet.be>
To: "Chris Marusich" <cmmarusich@gmail.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Authenticating maintenance.git
Date: Fri, 25 Jun 2021 14:26:03 +0200 [thread overview]
Message-ID: <6a4757b61e1cf6717aac88a654202087ff7e76c4.camel@telenet.be> (raw)
In-Reply-To: <87zgvg9ium.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]
Chris Marusich schreef op wo 23-06-2021 om 18:01 [-0700]:
> Although I was now able to run the pre-push hook, it seems unaware of my
> PGP key. I tried making the attached change to the README and testing a
> push via "git push -n origin", and it complained about the signature:
>
> --8<---------------cut here---------------start------------->8---
> $ git push -n origin
> Authenticating commits 8a7e10b to 413b8f1 (1 new commits)...
> [##############################################################################]guix git: error: could not authenticate commit 413b8f1c6d9ca2160d7aa8d80db181a6f39d3d82:
> key CBF5 9755 CBE7 E7EF EF18 3FB1 DD40 9A15 D822 469D is missing
> error: failed to push some refs to 'git.savannah.gnu.org:/srv/git/guix/maintenance.git'
> --8<---------------cut here---------------end--------------->8---
It is complaining about the missing key, not about signatures.
> GnuPG reports it can find the keys:
>
> --8<---------------cut here---------------start------------->8---
> $ gpg --list-keys 'CBF5 9755 CBE7 E7EF EF18 3FB1 DD40 9A15 D822 469D'
> [...]
The keyring in ~/.gnupg is irrelevant to "guix git authenticate".
"guix git authenticate" only uses the keys on the keyring branch
(whose fingerprint needs to be .guix-authorizations).
The public key is in .guix-authorization
(see https://git.savannah.gnu.org/cgit/guix/maintenance.git/tree/.guix-authorizations#n32).
But is it on the keyring branch?
It would appear it isn't. There is a marusich-D822469D.key, but
that appears to be a different key (DD40 9A15 D822 469D).
Perhaps you need to add your key to the keyring branch?
IIUC, commits to the keyring branch are unauthenticated, so
you could do that yourself. (It is secure because .guix-authorizations
contains a whitelist of allowed key fingerprints.)
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-06-25 12:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 11:03 Authenticating maintenance.git Ludovic Courtès
2021-05-06 21:26 ` Leo Famulari
2021-06-16 7:20 ` Chris Marusich
2021-06-20 16:25 ` Ludovic Courtès
2021-06-23 0:46 ` Chris Marusich
2021-06-24 1:01 ` Chris Marusich
2021-06-25 12:26 ` Maxime Devos [this message]
2021-06-29 14:36 ` Ludovic Courtès
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=6a4757b61e1cf6717aac88a654202087ff7e76c4.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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).