After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 589637 - Evolution insists on SHA1 signatures
Evolution insists on SHA1 signatures
Status: RESOLVED DUPLICATE of bug 304415
Product: evolution
Classification: Applications
Component: Mailer
2.26.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-07-24 18:57 UTC by Eric Hopper
Modified: 2009-07-25 02:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Eric Hopper 2009-07-24 18:57:57 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.
Comment 1 Matthew Barnes 2009-07-25 02:15:35 UTC
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 ***