From: Eric Bavier <bavier@posteo.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: New signing key
Date: Wed, 23 Jun 2021 16:05:06 +0000 [thread overview]
Message-ID: <cf86de62dd4a9f6e2c58f393a90afe9469b4031c.camel@posteo.net> (raw)
In-Reply-To: <871r8sy9n2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1647 bytes --]
On Wed, 2021-06-23 at 15:48 +0200, Ludovic Courtès wrote:
> Hi,
>
> Apologies for the delay!
>
> Eric Bavier <bavier@posteo.net> skribis:
>
> > I've updated my GPG key on Savannah with a new signing subkey and uid.
>
> Done in 3694c0d4fee0f7faf130ecd9386ea45932a19543.
Thank you Thank you!
> In
> d1d2bf3eb6ba74b058969756a97a30aec7e0c4d1 I added your new key and
> renamed the old one, but perhaps we can just remove the old one, if the
> old sub-key is still in the new one?
I think the old key is still there, yes. I didn't remove it, just
added the new key.
>
> Anyway, you should be able to push to ‘master’ now. Please double-check
> with ‘guix git authenticate’ (and the pre-push hook) that everything’s
> fine.
Will do.
>
> > Could a maintainer do the necessary repo updates?
>
> Note that any committer who’s checked that all is fine can do this, but
> I guess everyone was busy hacking (or reviewing!). ;-)
I completely understand. I didn't trust myself to know how to check
that all is fine. :)
>
> In the future, unless you lose control of the key, it’s even better if
> you do it yourself: push a commit signed with the old key that
> introduces the new key. Otherwise we have to trust that you really are
> the one who uploaded the new key on Savannah.
In this case, the old key had already expired. I think others here
have reset the expiry date on their keys before? I like the idea of
honoring the expiration dates I set, and creating a new key. But I'm
also willing to adopt whatever we decide is a best practice.
Thanks again,
`~Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2021-06-23 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 3:05 New signing key Eric Bavier
2021-06-22 21:52 ` Eric Bavier
2021-06-23 13:48 ` Ludovic Courtès
2021-06-23 16:05 ` Eric Bavier [this message]
2021-06-29 14:31 ` Ludovic Courtès
2021-06-29 14:40 ` Tobias Geerinckx-Rice
2021-06-29 16:06 ` Eric Bavier
2021-08-11 10:08 ` Ludovic Courtès
2021-08-17 7:46 ` zimoun
-- strict thread matches above, loose matches on Subject: below --
2023-07-24 2:26 Leo Famulari
2023-12-12 16:37 ` Maxim Cournoyer
2020-07-16 23:45 New Signing Key Brett Gilio
2020-07-18 19:35 ` Tobias Geerinckx-Rice
2020-03-05 17:13 New signing key Ludovic Courtès
2020-03-05 20:06 ` Roel Janssen
2020-03-05 20:16 ` Tobias Geerinckx-Rice
2018-04-23 18:20 Jan Nieuwenhuizen
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=cf86de62dd4a9f6e2c58f393a90afe9469b4031c.camel@posteo.net \
--to=bavier@posteo.net \
--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).