unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Markku Korkeala <markku.korkeala@iki.fi>
To: elaexuotee@wilsonb.com
Cc: guix-devel@gnu.org
Subject: Re: Losing signing keys for custom Guix channel
Date: Mon, 25 Mar 2024 09:49:46 +0200	[thread overview]
Message-ID: <ZgEsmghq7frMheBl@hai0398> (raw)
In-Reply-To: <3GFY4DFSZPFIH.26YI5TX7T5BW2@wilsonb.com>

On Mon, Mar 25, 2024 at 02:41:26PM +0900, elaexuotee@wilsonb.com wrote:
> Hey devs,
> 
> So I lost the PGP key that I was using to sign commits on a private Guix
> channel of mine. Is there a way to introduce a hard break in my channel
> authentication?
> 
> Despite updating authorization settings, pulls complain that my latest commit
> isn't signed by an authorized key.
> 
> Here are the changes I've made:
> - New public key added to keyring branch
> - Appended new key fingerprint to .guix-authorizations (at commit X)
> - Update introduction in .config/guix/channels.scm
>   - Point to commit X
>   - Update openpgp-fingerprint
> 
> As a sanity check, I've confirmed that the fingerprint on commit X, the
> fingerprint in .guix-authorizations, and the openpgp-fingerprint in my
> channels.scm are all the same.
> 
> What am I missing?

Hi all,

from reading about guix authentication I think the new signing key
must be first added to the .guix-authoriations file and that commit
must signed with the current signing keys before the new signing
key can be used.

Best wishes,
Markku


  reply	other threads:[~2024-03-25  7:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25  5:41 Losing signing keys for custom Guix channel elaexuotee
2024-03-25  7:49 ` Markku Korkeala [this message]
2024-03-25 12:31   ` Attila Lendvai
2024-03-28 22:47   ` Ludovic Courtès
2024-03-29  3:42     ` elaexuotee
2024-03-29  3:55       ` Jake
2024-03-29  5:06         ` elaexuotee
2024-03-29  9:45       ` Ludovic Courtès
2024-03-29 10:20         ` elaexuotee

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=ZgEsmghq7frMheBl@hai0398 \
    --to=markku.korkeala@iki.fi \
    --cc=elaexuotee@wilsonb.com \
    --cc=guix-devel@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).