I solved my issue so I'm posting this for the benefit of users who might
have the same issue.
I solved my issue my generating a new key pair because there seemed to
be no way to work around the incompatibility that caused the key to not
be able to sign on my NixOS machine. I'm not sure what ca
On Mittwoch, 24. Januar 2024 22:05:53 CET Leo Coogan via Gnupg-users wrote:
> It looks like there's only that non-functioning signing subkey. Huh. Do
> I need to create a new signing subkey?
Copy the content of ~/.gnupg/private-keys-v1.d from your fedora machine to
your nixox machine (after makin
Here's the command run on my fedora machine:
```
> gpg -K --list-options show-unusable-subkeys
/home/lcoogan/.gnupg/pubring.kbx
sec ed25519 2023-03-03 [SC] [expires: 2025-03-02]
C0156FFBE02B4E03F7792EB53D7F617CDE5C9A9B
uid [ultimate] Leo Coogan
On Tue, 23 Jan 2024 12:38, Leo Coogan said:
> sec# ed25519 2023-03-03 [SC] [expires: 2025-03-02]
> C0156FFBE02B4E03F7792EB53D7F617CDE5C9A9B
> Keygrip = 38953FFD2BD558606473A90A6EDD5B26F03FA3CB
You don't have a signing key. Ther primary key has been taken offline
('#') and can thus n
B00D9F
Keygrip = 02EE4AA6089E9DEF7792F548C01FFD8C05F1EC21
```
On 1/22/24 02:48, Werner Koch wrote:
Hi!
[GNUPG:] KEY_CONSIDERED C0156FFBE02B4E03F7792EB53D7F617CDE5C9A9B 2
gpg: writing to stdout
[GNUPG:] BEGIN_SIGNING H10
gpg: signing failed: Bad secret key
Plase run
gpg -K --with-subkey-fingerprint --with-keygrip
Oops, I meant to 'reply-all'.
Forwarded Message
Subject: Re: gpg: signing failed: Bad secret key
Date: Sun, 21 Jan 2024 13:02:40 -0500
From: Leo Coogan
To: Werner Koch
with `verbose` added to ~/.gnupg/gpg.conf:
```
git commit -m test
error:
On Fri, 19 Jan 2024 14:19, Leo Coogan said:
> When I run `git commit -m` on nixos, I receive this error:
For debugging add "verbose" to ~/.gnupg/gpg.conf . This should give you
more information what's up.
Shalom-Salam,
Werner
--
The pioneers of a warless world are the youth that
refuse mi
When I run `git commit -m` on nixos, I receive this error:
```
error: gpg failed to sign the data:
[GNUPG:] KEY_CONSIDERED C0156FFBE02B4E03F7792EB53D7F617CDE5C9A9B 2
[GNUPG:] BEGIN_SIGNING H10
gpg: signing failed: Bad secret key
[GNUPG:] FAILURE sign 67108871
gpg: signing failed: Bad secret key