When GpgOL uses the internal keycache the keys might have changed externally between caching and the actual crypto action.
So in case the crypto action fails with "unusable key" errors it would be nice if the keys would be flushed from the cache and the external resolution (which always uses up to date information) is used.
I give this low priority as I don't see a regular use case for deleting or otherwise messing (e.g. revoking) keys in the day to day use.
| rO GpgOL | |||
| rOfc05ec082038 Try to convert clearsigned to utf8 on verify fail | |||
| rO5f31ee9b15b3 Properly set UTF8 encoding for clearsigned | |||
| rOf46586d886cd Fix encoding for some inline pgp mails | |||
The reporter in the forum originally wrote:
If I delete the private PGP key in Kleopatra and use automatic sending, a error message “unusable secret key” appears. I have to close Outlook and start it again. Then it works.
This issue does still occur. Seen in VSD 3.3.2 with "normal" sending, i.e. without the "approval dialog always on" (I don't really know what was meant by "automatic sending"). You have to first send a mail to the key, then delete it and try again. It will not be fetched and you get the "unusable key" error.
Maybe we get rid of it if we finally change to a unified resolver?