Yesterday
Thu, Mar 14
Thanks for reporting this. Returning error codes to upper layers is not always easy because the original logic is that we have a global error counter to decide whether an operation succeeded. My fix to check the error code before emitting the DECRYPTION_OKAY status,
Wed, Mar 13
handle_plaintext gets data returned by iobuf_read, and does not check the error status of the iobuf object.
But only if you can figure out in a transaction or locked sytate whether the card needs a verify. Otherwise we have a race between changing the PIN and verifying a PIN.
This rejection could be relaxed.
Tue, Mar 12
needs to be fixed soon. But we don't have a tag for Gpg4win 5 or whatever we call a kf6 based gpg4win.
Mon, Mar 11
It could have been discussed whether this makes sense. However, we can't change it anymore because it would change the behaviour. Consider a cron job which looks into a directory with keyids and imports them from a keyserver. It is totally fine if the script returns success if no keys are available.
Sun, Mar 10
There is no way to recover it?
See T7034
Sorry, this is not a help line but a bug tracker. If you lost or forgot your password you are screwed up.
Sat, Mar 9
Fri, Mar 8
I have also not found a straightforward way to correct a cross-signature that was made with a weak digest algorithm using GnuPG.
Thu, Mar 7
Wed, Mar 6
I've sent you an email about it. It might have html elements due to markdown-here.
Sorry, for not following up earlier. Can you please do me a favor and run the last tests again, this time adding -v and --debug 1 to the invocation? Feel free to forward the output to my private address is that is easier (wk at gnupg.org).
Mon, Mar 4
How to test:
Thank you!
Applied to both (master and 1.10 branch).
Fri, Mar 1
Looks good to me. __CLOBBER_CC is needed as PA-RISC has carry/borrow bits in status register for add/sub instructions.
In 2.4 we have rG1383aa475 which does