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 <leocoogan@mailfence.com>
To: Werner Koch <wk@gnupg.org>
with `verbose` added to ~/.gnupg/gpg.conf:
```
> git commit -m test
error: gpg failed to sign the data:
gpg: enabled compatibility flags:
[GNUPG:] KEY_CONSIDERED C0156FFBE02B4E03F7792EB53D7F617CDE5C9A9B 2
gpg: writing to stdout
[GNUPG:] BEGIN_SIGNING H10
gpg: signing failed: Bad secret key
[GNUPG:] FAILURE sign 67108871
gpg: signing failed: Bad secret key
fatal: failed to write commit object
```
```
> pass insert test
An entry already exists for test. Overwrite it? [y/N] y
Enter password for test:
Retype password for test:
gpg: enabled compatibility flags:
gpg: using pgp trust model
gpg: using subkey 63D14EA6FDB00D9F instead of primary key 3D7F617CDE5C9A9B
gpg: automatically retrieved 'leocoogan@existential.beauty' via Local
gpg: using subkey 63D14EA6FDB00D9F instead of primary key 3D7F617CDE5C9A9B
gpg: This key belongs to us
gpg: reading from '[stdin]'
gpg: writing to '/home/lcoogan/.password-store/test.gpg'
gpg: ECDH/AES256.OCB encrypted for: "63D14EA6FDB00D9F Leo Coogan
(Personal) <leocoogan@existential.beauty>"
error: gpg failed to sign the data:
gpg: enabled compatibility flags:
[GNUPG:] KEY_CONSIDERED C0156FFBE02B4E03F7792EB53D7F617CDE5C9A9B 2
gpg: writing to stdout
[GNUPG:] BEGIN_SIGNING H10
gpg: signing failed: Bad secret key
[GNUPG:] FAILURE sign 67108871
gpg: signing failed: Bad secret key
fatal: failed to write commit object
```
And on my Fedora machine were the command runs successfully:
```
> pass insert test
An entry already exists for test. Overwrite it? [y/N] y
Enter password for test:
Retype password for test:
gpg: enabled compatibility flags:
gpg: using pgp trust model
gpg: using subkey 63D14EA6FDB00D9F instead of primary key 3D7F617CDE5C9A9B
gpg: automatically retrieved 'leocoogan@existential.beauty' via Local
gpg: using subkey 63D14EA6FDB00D9F instead of primary key 3D7F617CDE5C9A9B
gpg: This key belongs to us
gpg: reading from '[stdin]'
gpg: writing to '/home/lcoogan/.password-store/test.gpg'
gpg: ECDH/AES256.OCB encrypted for: "63D14EA6FDB00D9F Leo Coogan
(Personal) <leocoogan@existential.beauty>"
[master 6800a72] Add given password for test to store.
1 file changed, 0 insertions(+), 0 deletions(-)
```
Not sure if that helps much.
On 1/20/24 15:26, Werner Koch wrote:
> 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
>
-------- Forwarded Message --------
Subject: Re: gpg: signing failed: Bad secret key
Date: Sun, 21 Jan 2024 13:02:40 -0500
From: Leo Coogan <leocoogan@mailfence.com>
To: Werner Koch <wk@gnupg.org>
with `verbose` added to ~/.gnupg/gpg.conf:
```
> git commit -m test
error: gpg failed to sign the data:
gpg: enabled compatibility flags:
[GNUPG:] KEY_CONSIDERED C0156FFBE02B4E03F7792EB53D7F617CDE5C9A9B 2
gpg: writing to stdout
[GNUPG:] BEGIN_SIGNING H10
gpg: signing failed: Bad secret key
[GNUPG:] FAILURE sign 67108871
gpg: signing failed: Bad secret key
fatal: failed to write commit object
```
```
> pass insert test
An entry already exists for test. Overwrite it? [y/N] y
Enter password for test:
Retype password for test:
gpg: enabled compatibility flags:
gpg: using pgp trust model
gpg: using subkey 63D14EA6FDB00D9F instead of primary key 3D7F617CDE5C9A9B
gpg: automatically retrieved 'leocoogan@existential.beauty' via Local
gpg: using subkey 63D14EA6FDB00D9F instead of primary key 3D7F617CDE5C9A9B
gpg: This key belongs to us
gpg: reading from '[stdin]'
gpg: writing to '/home/lcoogan/.password-store/test.gpg'
gpg: ECDH/AES256.OCB encrypted for: "63D14EA6FDB00D9F Leo Coogan
(Personal) <leocoogan@existential.beauty>"
error: gpg failed to sign the data:
gpg: enabled compatibility flags:
[GNUPG:] KEY_CONSIDERED C0156FFBE02B4E03F7792EB53D7F617CDE5C9A9B 2
gpg: writing to stdout
[GNUPG:] BEGIN_SIGNING H10
gpg: signing failed: Bad secret key
[GNUPG:] FAILURE sign 67108871
gpg: signing failed: Bad secret key
fatal: failed to write commit object
```
And on my Fedora machine were the command runs successfully:
```
> pass insert test
An entry already exists for test. Overwrite it? [y/N] y
Enter password for test:
Retype password for test:
gpg: enabled compatibility flags:
gpg: using pgp trust model
gpg: using subkey 63D14EA6FDB00D9F instead of primary key 3D7F617CDE5C9A9B
gpg: automatically retrieved 'leocoogan@existential.beauty' via Local
gpg: using subkey 63D14EA6FDB00D9F instead of primary key 3D7F617CDE5C9A9B
gpg: This key belongs to us
gpg: reading from '[stdin]'
gpg: writing to '/home/lcoogan/.password-store/test.gpg'
gpg: ECDH/AES256.OCB encrypted for: "63D14EA6FDB00D9F Leo Coogan
(Personal) <leocoogan@existential.beauty>"
[master 6800a72] Add given password for test to store.
1 file changed, 0 insertions(+), 0 deletions(-)
```
Not sure if that helps much.
On 1/20/24 15:26, Werner Koch wrote:
> 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
>