unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Kehayias <john.kehayias@protonmail.com>
To: Andrew Tropin <andrew@trop.in>
Cc: guix-devel@gnu.org, "Maxime Devos" <maximedevos@telenet.be>,
	"Tobias Geerinckx-Rice" <me@tobias.gr>,
	"Efraim Flashner" <efraim@flashner.co.il>,
	"Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [POSTMORTEM] Subkey is not authorized by .guix-authorizations
Date: Thu, 11 Aug 2022 15:25:32 +0000	[thread overview]
Message-ID: <YBuzYA7YC8Y9Q77jyJydqmLaM8Vd8TnC1x8iL9p-prvMSQ2F5VDuNnZOxBQdeiQ49VXfUGRik0auTTFejqtU-f8iiWDGUCNGhl_cG1Ez55E=@protonmail.com> (raw)
In-Reply-To: <46ba22ef-6b47-fec0-5397-64401f5c7983@telenet.be>

Hi everyone,

Thanks for this write-up and discussion Andrew. I'm also following along in [0] but I'll just chime in here for now.

When I saw this I was worried since I also "just" use subkeys, meaning for all signing etc. only my subkey is used. These are set to expire each year and then I renew them. For places like GitLab/Hub, this requires deleting the public key and re-adding it after I renew keys. Old commits still show as verified.

Anyway, that's my basic usage and I was worried that I would break a (third party) Guix channel when I was added as a committer. Indeed, that is what just happened, with the same steps: my primary key fingerprint was added to .guix-authorizations. GitLab was happy enough verifying the (subkey signed) commits, and even Cuirass would get the commits and build them. (Side note: does Cuirass not do guix pull? Why would it not fail to pull just as a user?)

All that is to say that I think the use case of someone only using subkeys is valid and one we could expect and should handle. Now, the correct and best way to do that, especially with things like time-travel, I don't know. I just wanted to note that I think only expecting the primary key (rather than subkeys) is limiting.

Finally, as a concrete example of this usage, I manage my keys with a hardware key (YubiKey) and followed this [1] guide to setting up with subkeys that I renew regularly. The primary key isn't really used for much and I think this works well, all I manage is renewal every so often. 

[0] https://issues.guix.gnu.org/57091 

[1] https://github.com/drduh/YubiKey-Guide

John


  reply	other threads:[~2022-08-11 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 14:26 [POSTMORTEM] Subkey is not authorized by .guix-authorizations Andrew Tropin
2022-08-11 15:09 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2022-08-11 15:11 ` Maxime Devos
2022-08-11 15:25   ` John Kehayias [this message]
2022-09-02 13:23 ` Ludovic Courtès
2022-09-05  7:07   ` Andrew Tropin
2022-09-05  9:53     ` Ludovic Courtès
2022-09-05 11:50       ` Tobias Geerinckx-Rice

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='YBuzYA7YC8Y9Q77jyJydqmLaM8Vd8TnC1x8iL9p-prvMSQ2F5VDuNnZOxBQdeiQ49VXfUGRik0auTTFejqtU-f8iiWDGUCNGhl_cG1Ez55E=@protonmail.com' \
    --to=john.kehayias@protonmail.com \
    --cc=andrew@trop.in \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    --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 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).