* Kevin J. McCarthy <[email protected]> [2015-07-12 19:20 -0400]:
This patch came from a bug report on IRC from "ep". He noticed Mutt was hardcoding the micalg parameter to sha1, but his actual signature digest was using sha256. Because of this, Thunderbird was rejecting the signature.
Ok.
Another possibility is to let the Mutt user instead specify the signature digest algorithm they want to use. This patch takes that route. The downside to this is that the revised $smime_sign_command, with a '-md %d' needs to be used or else the generated signature (again) won't match the value stored in micalg. Smime users, and ep if you're out there, please help me test this and provide feedback.
I have not tried to modify the default algorithm yet (no time today other than the initial patch and install), however I have used the patch to sign emails to myself and others and compared the claimed algorithm used. Without the patch today's tip show's SHA-1 as the algorithm, with the patch the algorithm today's tip show's SHA-256 as the algorithm. Tomorrow (or Sunday) I'll take a look at the signatures in Thunderbird, and look at the extracted algorithms. I'll also try setting the digest alrogithm manually tomorrow, and report back. Let me know if there are any other specific things I need to look for, other than mismatches. -- dave [ please don't CC me ]
signature.asc
Description: PGP signature
