all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Bavier <bavier@posteo.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: New signing key
Date: Tue, 29 Jun 2021 16:06:53 +0000	[thread overview]
Message-ID: <264ead6a500acc3a15b78d8eeae48d668b4e3333.camel@posteo.net> (raw)
In-Reply-To: <87eeckbs8d.fsf@nckx>

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

Hi Tobias,

On Tue, 2021-06-29 at 16:40 +0200, Tobias Geerinckx-Rice wrote:
> Question: I think committers should be trusted with discretion in 
> how they prefer to manage their keys, but how about briefly 
> documenting a suggested sane key-management strategy to new 
> committers, like we already describe some rando's editor set-up? 
> :-)

I think this would be very nice. Especially if it laid out some of the
trade-offs as you did here.

> 
> I don't think most people *insist* on their current one, it's just 
> what they know; and GPG is complex and gnarly.
> 
...
> 
> I'm not aware of any authority on best practices that would claim 
> the opposite, but if you are, I'd be grateful to hear about it!
> 

No, I definitely fall into the group who don't insist on a strategy and
are just doing what they know :).  I appreciate your feedback!  And
I'll probably be making some adjustments to my workflow.

Thanks,

`~Eric

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]

  reply	other threads:[~2021-06-29 16:08 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
2021-06-29 14:31     ` Ludovic Courtès
2021-06-29 14:40       ` Tobias Geerinckx-Rice
2021-06-29 16:06         ` Eric Bavier [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=264ead6a500acc3a15b78d8eeae48d668b4e3333.camel@posteo.net \
    --to=bavier@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.