GNOME Bugzilla – Bug 589637
Evolution insists on SHA1 signatures
Last modified: 2009-07-25 02:15:35 UTC
Please describe the problem: I set up my .gnupg/options file to have this entry digest-algo SHA256 and after that signatures produced by mutt are created using SHA256. But signatures created by evolution still use SHA1. Steps to reproduce: 1. Compose and send a signed message 2. Check the signature on that message 3. Notice that it is an SHA1 signature Actual results: My message is signed with an SHA1 signature Expected results: My message being signed with an SHA256 signature Does this happen every time? Yes Other information: SHA1 is broken and I want to stop using it. I don't care if recipients won't be able to check my signature. I want them to check a signature that's secure with reasonably modern software, not a signature that's potentially fake because it uses a broken algorithm.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 304415 ***