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.
Mon, Nov 11
Thu, Nov 7
Oct 4 2019
Sep 9 2019
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! :-)
Jun 13 2019
I have a larger change for the wait code in the works. This will go into 1.14.0 but not in 1.13.1
Jun 7 2019
Jun 6 2019
I had to patch strace to follow threads but not forks (P8) and then when built with support for -k I tracked it down: In the inbound handler we close the fd immediately on EOF. However the upper layers don't know about it and a select fails with EBADF. Of course we could ignore the EBADF, figure out the closed fd and restart. The problem is that another thread may have opened a new oobject and that will get the last closed fd assigned - bummer.
Just noticed that due to me failing to properly understand re-entrant locks the run-thread test is broken at least on windows in that it never waits for completion. So running out of filedescriptors is to expect. I'll fix the test.
My observation from running the verify threaded test on windows is that it does behave differently. The EBADF does not occur.
Jun 5 2019
Something(tm) closes an arbitrary file descriptor behind our back. Not easy to track down because strace can not trace only threads - it always wants to trace all children as well - which is a bit too much and leads to other problems.
Jun 4 2019
Jun 3 2019
A newline is required by the PEM standard.
May 29 2019
Thanks, the mentioned OpenSSL option should be helpful.
A high level test description is:
- Configure both gpgsm and dirmngr to use OCSP.
- Import the responder signer certificate with gpgsm --import.
- Use a certificate with OCSP responder extension present, or configure a default OCSP responder in dirmngr.
- Configure your OCSP responder to identify itself with key ID (and not subject name)
- Attempt to sign or verify with gpgsm.
- You should get an error, with dirmngr logs showing that the responder signer certificate could not be found.
Thank you for a quick fix (despite this being a minor problem).
May 28 2019
Do you have any test cases? Note that T3966 is due to missing support for SHA-256.
We only supported SHA-1 signed OCSP requests. Fix will go into 2.2.16.
May 27 2019
Thanks to your very good analysis, this was easy to fix.
May 24 2019
Interesting tinge: The main CRL of the dgn.de CA uses a nextUpdate in the year 2034 (15 years in the future) which would force dirmngr to cache the CRL until then. However, the CRL of the intermediate certificate has a nextUpdate only one month in the future. There is currently no entry in that second level CRL, so their idea might be that an updated second level CRL will also trigger a reload of the main CRL. I have not checked how we implement that in Dirmngr but I doubt that such a thing will work for us and that it is in any way standard compliant.
May 16 2019
That was obvious. rG6fc5df1e10129f3171d80cf731f310b9e8d97c26 fixes this.
When doing a "gpgsm --with-validation -k foo" (assuming you have a cert foo) gpgsm now goes into a loop and prints the certficates that match "foo" over and over again. I have not tested if it was caused by this change but I think it is likely.
I imported 39 certificate files at once with Kleopatra with about 700 certificates and it worked. Took a long time though so It would be nice if Kleopatra would show a progess indicator or some indication that the import is running. But this is a different issue.
May 15 2019
Will give you more detailed info about your certificate. For even more details use --dump-chain instead of --list-chain.
May 14 2019
The last lines that the process currently holding wrote in the log:
To reproduce this issue I started Kleopatra with an empty GNUPGHOME and imported 10 S/MIME certs at once (which spawns a gpgsm process each) with enabled logging.
Thanks for the hint on the existing OID I already looked into that and planned to use one from the GnuPG arc, But an existing OID is better. I still need to figure useful workflows but something like this will be useful for smartcards..
May 13 2019
May 12 2019
May 3 2019
Mar 27 2019
I forgot: Instead of importing the missing internal CA, this works:
I agree, the question is which CRL is checked when how. Maybe there is some mistake on my side. Here is a recipe for Debian:
I don't think this is a bug. Failure to encrypt when CRL check fails is expected.
Mar 26 2019
Mar 14 2019
Mar 4 2019
Ouch indeed. Looks like you run into a "hanging" gpg-agent situation in that case our main background process is blocked and all other processes wait for it to respond and nothing works anymore.
This should never happen and we need to fix it. But so far we have not found a way to reproduce it.
Feb 28 2019
Looking at other threads I found the problem in some .lock file in my gnupg directory. One of them was locked by a running process and I was not able to delete. So I opened up task manager and I had dozens of gnupg related processes running. I killed all of them and removed any .lock file.
This way Kleopatra started again but the certificate above (aruba) was not present in the imported ones. And, of course, I'm not going to import it anymore, will use my sixt sense to trust certificates...
The exact file that created the lock is attached.
I zipped it to avoid an unintended import that kills Kleopatra.
The only action I can do is quit the program telling it to stop the background actvity, but I cannot use it anymore...
Ouch, worse problem here. After closing kleopatra telling it to stop doing whatever it was, I restarted the application and now it's stuck in "Loading certificate cache"
The certificate was defintely missing the tag lines, thanks. I also tried opening the certificate from that page (Windows has no problems without the tag lines) and exporting it explicitly as base64, and the output file is fine.
The problem is that the import now seems to go well, but no certificate is imported at all. I tried several times and the import box just closes after selecting the file.
I tried to close Kleopatra and it says there are ongoing background operations. At least 15 mins passed between the import and the closing tentative.
Actually, it is stuck doing something.
Thanks for the report.
Btw. I only noticed this now as I always had "disable-tor" in my config but recently removed it for testing.
Feb 27 2019
We also need to fix for encryption and signature in CSR.
Feb 18 2019
Feb 15 2019
Feb 14 2019
Thanks for that summary.
Feb 13 2019
Since it seems there is a renewed interest in adding ECC support to GpgSM (as indicated by the T4098 feature request), I would like to write down here more details about this task.
Feb 6 2019
See also T4013 which is about ed25519 key support
Dec 18 2018
I'm the spanish user. Are you also setting default ocsp responder option?
Setting only ocsp_signer doesn't worked, there are several CA's with diferent ocsp responders.
The reporter said that it did not work for him.
Dec 17 2018
A list of SHA-1 fingerprints for the valid certificates. With our without colons.
@werner what should the contents of the file look like?
I had to look it up in the code and man page too ;-)
Good to know. I thought that ocsp-signer was only used if ocsp-responder is explitly set. I've suggested the workaround in the Message Board.
In Wald someone reports that this also appears to happen when decrypting. https://wald.intevation.org/forum/message.php?msg_id=6377 Probably run-threaded will help to flush this out.