Re: Error / feature-request: Signing git commits with SSH hardware key

From: Fabian Stelzer <fs@gigacodes.de>
Date: Oct 12, 2022, 06:55 UTC
Message-ID: <20221012065541.y2tl63tw3ooeoy7s@fs>
In-Reply-To: <87r0zeuhrv.fsf@ngraves.fr>

On 12.10.2022 00:17, Nicolas Graves wrote:

Show 9 quoted lines

>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

Show 7 quoted lines

>
>Thanks for your help!
>
>
>-- 
>Best regards,
>Nicolas Graves