'No pinentry' error (--pinentry-mode loopback with --delete-secret-and-public-key)

[Carola Grunwald]

Hello Dashamir,

on Tue, 10 May 2016 04:17:07 +0200, you wrote:

>On Sat, May 7, 2016 at 5:32 PM, Carola Grunwald <caro at nymph.paranoici.org>
>wrote:
>
>>
>> You're right, there's no passphrase request with
>>
>> | d:\gpg>gpg.exe --batch --homedir "d:\gpgdat" --no-auto-key-locate
>> --no-default-keyring --keyring "d:\gpgdat\pubring.kbx"
>> --delete-secret-and-public-key "66C040ADBE2C5728022F81DCCE09E0556C2C8CE0"
>>
>> But that way a 'Pinentry' window opens, which I have to avoid:
>>
>> | Pinentry
>> |
>> | Do you really want to permanently delete the
>> | OpenPGP secret key:
>> | "John Doe <doej at example.com>"
>> | 2048-bit RSA key, ID 6C2C8CE0,
>> | created 2016-04-23.
>> | ?
>> |
>> |                [ Delete key ] [     No     ]
>>
>> followed by
>>
>> | Pinentry
>> |
>> | Do you really want to permanently delete the
>> | OpenPGP secret subkey key:
>> | "John Doe <doej at example.com>"
>> | 2048-bit RSA key, ID 174B70A0,
>> | created 2016-04-23 (main key ID 6C2C8CE0).
>> | ?
>> |
>> |                [ Delete key ] [     No     ]
>>
>
>I agree, this is anoying. And the docs say that with --batch and --yes and
>"fingerprint" no questions will be asked (this is the meaning of batch
>after all).

Meanwhile I'm sure it's a bug similar to
https://bugs.gnupg.org/gnupg/issue2324.

GnuPG 2.1 isn't ready for embedded usage yet.
It's still experimental, so we have to wait.

>But I just realized that you can delete everything on
>"$GNUPGHOME/private-keys-v1.d/" and all the private keys will be deleted,
>no questions asked. This is simpler and cleaner.

That's not future-proof.
When GPG caches file system data it may fail.

Kind regards

Caro