git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fabian Stelzer <fs@gigacodes.de>
To: Marcos Alano <marcoshalano@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Unable to use security key to commit signing using SSH keypair
Date: Tue, 28 Jun 2022 18:23:42 +0200	[thread overview]
Message-ID: <20220628162342.ootjobbjtxg7b7ay@fs> (raw)
In-Reply-To: <97adcd90-b4d3-1114-205b-3445dd48b497@gmail.com>

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/id_ed25519_sk.pub)"

Did you try just putting the public keys path into user.signingkey?
Literal keys would need to be prefixed with `key::`

git config --global user.signingkey ~/.ssh/id_ed25519_sk.pub
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 sk-ssh-ed25519@openssh.com <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

  reply	other threads:[~2022-06-28 16:32 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 [this message]
2022-06-28 16:43   ` Marcos Alano

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=20220628162342.ootjobbjtxg7b7ay@fs \
    --to=fs@gigacodes.de \
    --cc=git@vger.kernel.org \
    --cc=marcoshalano@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).