From: Nicolas Graves <ngraves@ngraves.fr>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, Cuckoo Aidan <aidancuckoo@gmail.com>
Subject: Re: Error / feature-request: Signing git commits with SSH hardware key
Date: Tue, 11 Oct 2022 23:54:27 +0200 [thread overview]
Message-ID: <87v8oquiuk.fsf@ngraves.fr> (raw)
In-Reply-To: <Y0XVCDu9o3xDnt81@tapette.crustytoothpaste.net>
On 2022-10-11 20:41, brian m. carlson wrote:
> Could you maybe mention what version of OpenSSH you're using and on what
> platform? I used 9.0p1, and as I mentioned, it's Linux. The output
> looks like so:
I currently use this version on Guix (so Linux):
OpenSSH_8.9p1, OpenSSL 1.1.1q 5 Jul 2022
The errors occurs when I try to "really" commit using magit or git
through the command line.
hint: Waiting for your editor to close the file...
Waiting for Emacs...
error: Couldn't load public key sk-ssh-ed25519@openssh.com AAAAG[..]zaDo=: No such file or directory?
fatal: failed to write commit object
Now if I try this command:
> $ git verify-commit --raw HEAD
I get the following:
error: gpg.ssh.allowedSignersFile needs to be configured and exist for ssh signature verification
It's possible that my config is not complete, I remember not having
necessarily done the part with allowedsigners (which is not necessary
for an ed25519 "simple" key apparently). I'll take a look, and come back
to you.
--
Best regards,
Nicolas Graves
next prev parent reply other threads:[~2022-10-11 22:31 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 [this message]
2022-10-11 22:17 ` Nicolas Graves
2022-10-12 6:54 ` Nicolas Graves
2022-10-12 6:55 ` Fabian Stelzer
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=87v8oquiuk.fsf@ngraves.fr \
--to=ngraves@ngraves.fr \
--cc=aidancuckoo@gmail.com \
--cc=git@vger.kernel.org \
--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