Many operations fail due to changes in gnupg 2.0.27
Reported by Luke Le | March 27th, 2015 @ 03:05 PM | in 0.5 (closed)
In gnupg 2.0.27 keys using a weak digest algorithm like MD5
report a fingerprint of all 0s.
If the users adds the option "allow-weak-digest-algos" the
fingerprint is reported correctly and thus the keys are treated
correctly.
For some reason, this change also affects the handling of other gpg keys which don't use the MD 5 digest algorithm.
One possibility would be to pass allow-weak-digest-algos to affected gpg operations from Libmacgpg, but that's probably defeating the purpose.
Comments and changes to this ticket
-
-
-
steve March 31st, 2015 @ 03:19 PM
- State changed from “new” to “fixed”
- Assigned user set to “Mento”
- Milestone set to “0.6”
-
steve April 12th, 2015 @ 01:43 PM
- State changed from “fixed” to “verified”
-
steve June 18th, 2015 @ 12:34 PM
- Milestone changed from “0.6” to “0.5”
-
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Alex (via GPGTools)
Luke Le
steve