archive mirror
 help / color / mirror / Atom feed
From: Marcos Alano <>
To: Fabian Stelzer <>
Subject: Re: Unable to use security key to commit signing using SSH keypair
Date: Tue, 28 Jun 2022 13:43:43 -0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20220628162342.ootjobbjtxg7b7ay@fs>

On 28/06/2022 13:23, Fabian Stelzer wrote:
> On 27.06.2022 21:09, Marcos Alano wrote:
>> Hello fellows!
>> I'm able to sign commits using SSH keypair, but the keypair must be 
>> located in a file. If I try to use a SSH keypair in a security key 
>> (like an YubiKey) I get an error. I used this commands to do the test:
>> ```
>> ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_sk
>> git config --global gpg.format ssh
>> git config --global user.signingkey "$(cat ~/.ssh/"
> Did you try just putting the public keys path into user.signingkey?
> Literal keys would need to be prefixed with `key::`
Thank you, worked like a charm. Every documentation I read told me to 
use the plain public key, without the path or the prefix you indicated. 
And worked well with a regular keypair.

Using the path and prefixing the public key worked.

You have my gratitude. :)

Stay well,
> git config --global user.signingkey ~/.ssh/
> should be just fine.
> Also, the private key needs to be available in your ssh agent. If in 
> doubt you can check with a `ssh-add -L`.
>> git commit -S --allow-empty --message="Testing"
>> ```
>> Bnd I get this error:
>> ```
>> error: Couldn't load public key <my key 
>> id>: No such file or directory?
>> fatal: failed to write commit object
>> ```
>> I did the same thing with a plain ed25519 keypair and worked.
>> Am I doing anything wrong or security keys aren't supported yet?
>> Thank you for any help,
>> -- 
>> Marcos Alano

Marcos Alano

      reply	other threads:[~2022-06-28 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28  0:09 Unable to use security key to commit signing using SSH keypair Marcos Alano
2022-06-28 16:23 ` Fabian Stelzer
2022-06-28 16:43   ` Marcos Alano [this message]

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:

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

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).