Re: [Mutt] #3339: S/MIME Certificate Import Failures

#3339: S/MIME Certificate Import Failures -+- Reporter: adian | Owner: mutt-dev Type: defect | Status: new Priority: major | Milestone: Component: mutt|Version: 1.5.20 Resolution: | Keywords:

Re: [Mutt] #3559: smime_keys.pl considers only first certificate of a chain

#3559: smime_keys.pl considers only first certificate of a chain -+-- Reporter: andy| Owner: mutt-dev Type: defect | Status: new Priority: minor | Milestone: Component: crypto |Version: 1.5.21 Resolution: | K

[PATCH] smime_keys: Handle certificate chains in add_cert. (closes #3339) (closes #3559)

Attached is a patch which hopefully implements better certificate chain handling for add_cert. Although I've tried to test it, I am not a S/MIME user and don't have access to a large number of certificates to play with. I would greatly appreciate if smime_keys users would help me test this out.

Re: choices in crypt-gpgme.c

* Derek Martin [2015-05-18 12:34 -0400]: Yes and no... IIRC in that thread I actually pointed out several older related bugs. The actual orignal bug was: http://dev.mutt.org/trac/ticket/1022 That bug is hard to find in the archives though, and the bug itself in trac is somehow a mishmash of

Re: Certificate chain handling in smime_keys (was "[PATCH] smime_keys: convert openssl execution ...")

* Kevin J. McCarthy [2015-05-18 18:10 -0400]: Okay. That's good to know, so the add_cert should allow multiple leafs and a possibly shared intermediate cert. I have more carefully reviewed the code in smime.c and have found nothing that appears to check the purpose of the certs. If it finds m