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 314037 - default hash algorithm in gpg options ignored
default hash algorithm in gpg options ignored
Status: RESOLVED DUPLICATE of bug 304415
Product: evolution
Classification: Applications
Component: general
2.2.x (obsolete)
Other other
: Normal normal
: ---
Assigned To: Harish Krishnaswamy
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-08-20 15:37 UTC by fischi
Modified: 2005-08-22 03:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description fischi 2005-08-20 15:37:44 UTC
Distribution: Debian 3.1
Package: Evolution
Severity: normal
Version: GNOME2.10.2 2.2.x
Gnome-Distributor: Debian
Synopsis: default hash algorithm in gpg options ignored
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 2.2.x
Description:
Description of Problem:
Evolution ignores the default hash algorithm. It should not add the
"--digest-algo=SHA1" option to the gpg commandline. Otherwise there
should by a way to change this in Evolution.

Steps to reproduce the problem:
1. add "digest-algo SHA256" to .gnupg/options
2. compose a signed mail

Actual Results:
The Mail is signed with SHA1.

Expected Results:
Signed with SHA256 (the default in the options file).

How often does this happen?
always

Additional Information:
The same problem is possibly with the preferred encryption
algorithm....
Signing files directly with gpg works fine (using SHA256).




------- Bug moved to this database by unknown@gnome.bugs 2005-08-20 15:37 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was ibf_c@web.de.

Comment 1 André Klapper 2005-08-20 23:55:05 UTC
adding keyword
Comment 2 Not Zed 2005-08-22 03:45:58 UTC
this isn't very easy to fix.  we need to know the hash algorithm before we
create the message because it is part of the mail headers.

we can't just leave it out and let the other end guess.
Comment 3 Not Zed 2005-08-22 03:53:10 UTC

*** This bug has been marked as a duplicate of 304415 ***