unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jgart <jgart@dismail.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: guix git authenticate throws hard
Date: Wed, 26 Oct 2022 19:07:40 -0500	[thread overview]
Message-ID: <20221026190740.GB15216@dismail.de> (raw)
In-Reply-To: <0395BB1B-3B58-493F-BC74-25810A47098F@lepiller.eu>

On Wed, 26 Oct 2022 09:07:57 +0200 Julien Lepiller <julien@lepiller.eu> wrote:
> It says fingerprint, so it's fingerprint. Using email or name would not be as secure.
> 
> Le 26 octobre 2022 07:35:20 GMT+02:00, jgart <jgart@dismail.de> a écrit :
> >On Wed, 26 Oct 2022 07:21:35 +0200 Julien Lepiller <julien@lepiller.eu> wrote:
> >> From the manual: "signer is the OpenPGP fingerprint of public key used to sign commit.", but we should still catch this error :)
> >
> >Is it possible to give the email instead of the fingerprint?
> >
> >Deduce the fingerprint from the email?

Julien and/or anyone else,

What do you think if we have a CLI flag for git authenticate that would
allow us to do this to authenticate the last 5 commits against the
3B1D7F19E36BB60C0F5B2CA9A52AA2B477B6DD35 fingerprint, for example:

guix git authenticate 3B1D7F19E36BB60C0F5B2CA9A52AA2B477B6DD35 -5

I've run into situations where I can't remember if I signed a commit or not. 

IWBC if I could just say authenticate the last commits against my
fingerprint instead of going one by one. If this already exists and is
not documented then we should definitely document that usage with an
example to let others know.

all best,

jgart


  reply	other threads:[~2022-10-27  0:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  2:33 guix git authenticate throws hard jgart
2022-10-26  5:21 ` Julien Lepiller
2022-10-26  5:35   ` jgart
2022-10-26  7:07     ` Julien Lepiller
2022-10-27  0:07       ` jgart [this message]
2022-10-27  0:09         ` jgart
2022-10-27  5:23         ` Julien Lepiller

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=20221026190740.GB15216@dismail.de \
    --to=jgart@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    /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).