Sat, Feb 15
Fixed in master and 2.2
Really interesting: The code didn't changed since since 2003 and the bug must have been there all the time. It does happen only for 25% of the certificates with CR and LF; the others have padding characters at the end '=' which is also an indication of the end of the base64 block. I wonder why this has not been reported more often; maybe because most people import binary certificates.
Wald certificate will be fixed very soon. But as it is not fixed yet, I provided an http link, not https for you.
Thomas, please provide a sample certificate. I can't access the intevation site to see whether one of the links has the cert. And pretty please fix the wald certificates!
Mon, Feb 3
Hi Andre, did you already get anywhere with this task? Thanks a lot in advance, Joachim
Dec 17 2019
The description comes from gpg/gpgsm while the prompts are from gpg-agent. Thus if the agent has been started with the German local but gpgsm without a local this would explain the behaviour.
Dec 7 2019
Dec 6 2019
I found a solution for master and 2.1.19 which minimizes the risk of regressions:
Dec 5 2019
I think this is now resolved.
Dec 4 2019
Very few OpenPGP data signatures have an expiration time either, fwiw. I have never actually seen one in the wild, and no one that i know uses --ask-sig-expire or --default-sig-expire (it shows up in the cupt test suite and the apt test suite, but doesn't appear to be actually used by anything).
CMS signatures do not have a expiration time. Further the meaning of the expiration time of one of the certificates also depends on the validation model (shell or chain); thus a one-to-one relationship between these times is not possible.
Dec 3 2019
I uploaded the certificate files. For a test please do the following:
Nov 27 2019
Sorry, a fix didn't made it into 2.2.18.
Nov 26 2019
Nov 25 2019
Nov 21 2019
Nov 11 2019
Nov 7 2019
Oct 4 2019
Sep 9 2019
I give this normal priority even if it is a whish because I have the same whish and already have some code around that would make it more comfortable, especially if it is used directly in GpgOL.
Sep 5 2019
Thanks for the sample certs. I noticed the posts but had not the time to look into them.
Aug 22 2019
It appears (for me) correct behavior.
Jul 5 2019
Works for me! :-)