Re: Signing failed -- "No secret key", even though I have the key

2017-09-24 Thread Juan Miguel Navarro Martínez
On 2017-09-24 at 17:34, azarus wrote: > This is what gpg -K lists: > > /home/azarus/.gnupg/pubring.kbx > --- > sec rsa4096 2016-12-20 [SC] > > uid [ultimate] > uid [ultimate] > ssb rsa4096 2016-12-20 [E] > ssb# rsa4096 2017-06-23 [SE]

Re: Signing failed -- "No secret key", even though I have the key

2017-09-24 Thread Kristian Fiskerstrand
On 09/24/2017 05:34 PM, azarus wrote: > ssb# rsa4096 2017-06-23 [SE] > > Can somebody explain what I'm doing wrong? A combined sign and encrypt capable subkey would be wrong #1, you likely want to revoke this one and generate separate subkeys for the various options. Aditionally, they are stub

Signing failed -- "No secret key", even though I have the key

2017-09-24 Thread azarus
Hello GPG users, I have a problem regarding signing data. Whenever I try clear-signing, this appears: gpg: writing to stdout -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 hello gpg: signing failed: No secret key gpg: [stdin]: clear-sign failed: No secret key I invoked clearsign like this: ec