unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: elaexuotee@wilsonb.com
To: Jake <jforst.mailman@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Losing signing keys for custom Guix channel
Date: Fri, 29 Mar 2024 14:06:56 +0900	[thread overview]
Message-ID: <20KIFQVN9LJD2.3CQ6GR6DPRLJC@wilsonb.com> (raw)
In-Reply-To: <CAJqVjv92MVFOR1_cfe6xCwjD-+oEk2tipdUeM9+SRNTRThhC3Q@mail.gmail.com>

Jake <jforst.mailman@gmail.com> wrote:
> If commit i adds a new signing key to the channel’s authorisations file and
> commit i+1 is signed with that signing key, then commit i+1 can be used in
> channel intro.
> 
> You can’t add a signing key to the authorisations in a commit and sign that
> same commit with the new key.  Is that issue here?

I don't think that's completely accurate. My original channel introduction
commit is precisely the one creating a .guix-authorizations file with my old
key info.

I can certainly add an extra signing key to the authorizations; I just can't
sign that commit with the old key, since the old key has been lost.


  reply	other threads:[~2024-03-29  5:07 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
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 [this message]
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=20KIFQVN9LJD2.3CQ6GR6DPRLJC@wilsonb.com \
    --to=elaexuotee@wilsonb.com \
    --cc=guix-devel@gnu.org \
    --cc=jforst.mailman@gmail.com \
    /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).