From: Fabian Stelzer <fs@gigacodes.de>
To: Nicolas Graves <ngraves@ngraves.fr>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org, Cuckoo Aidan <aidancuckoo@gmail.com>
Subject: Re: Error / feature-request: Signing git commits with SSH hardware key
Date: Wed, 12 Oct 2022 08:55:41 +0200 [thread overview]
Message-ID: <20221012065541.y2tl63tw3ooeoy7s@fs> (raw)
In-Reply-To: <87r0zeuhrv.fsf@ngraves.fr>
On 12.10.2022 00:17, Nicolas Graves wrote:
>On 2022-10-11 23:54, Nicolas Graves wrote:
>
>> error: gpg.ssh.allowedSignersFile needs to be configured and exist for ssh signature verification
>
>And I can confirm that it was this error and bad configuration, sorry!
>
>> error: Couldn't load public key sk-ssh-ed25519@openssh.com AAAAG[..]zaDo=: No such file or directory?
>
>This error is not very precise though.
I assume you have specified your key in the git config in user.signingkey as
the literal keystring?
If so, then you'll need a `key::` prefix. Otherwise git will treat it as a
file path.
See
https://git-scm.com/docs/git-config#Documentation/git-config.txt-usersigningKey
In the initial merge of this feature, git would allow ssh-* keys to be
specified without the prefix. This was later deprecated and not all
Tutorial/Docs you'll find online consider this.
Cheers,
Fabian
>
>Thanks for your help!
>
>
>--
>Best regards,
>Nicolas Graves
next prev parent reply other threads:[~2022-10-12 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 18:12 Error / feature-request: Signing git commits with SSH hardware key Nicolas Graves
2022-10-11 20:41 ` brian m. carlson
2022-10-11 21:54 ` Nicolas Graves
2022-10-11 22:17 ` Nicolas Graves
2022-10-12 6:54 ` Nicolas Graves
2022-10-12 6:55 ` Fabian Stelzer [this message]
2022-10-12 7:22 ` Nicolas Graves
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=20221012065541.y2tl63tw3ooeoy7s@fs \
--to=fs@gigacodes.de \
--cc=aidancuckoo@gmail.com \
--cc=git@vger.kernel.org \
--cc=ngraves@ngraves.fr \
--cc=sandals@crustytoothpaste.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox