Page MenuHome GnuPG
Create Task
Maniphest T389

Cannot select digest-algo with symmetric encryption
Closed, ResolvedPublic
Actions

Description

Release: 1.3.93

Environment

Debian GNU/Linux (Sarge).
i686

Description

I am unable to specify my choice of digest algorithim with the development release 1.3.93 when performing symmetric encryption (-c). When I have ripemd160 specified as my s2k-digest in gpg.conf (my normal configuration), this overrides any alternative preference I give on the command line with --digest-algo. When I remove the s2k-digest line in gpg.conf, sha1 overrides any --digest-algo contents I give on the command line. Assymmetric encryption works flawlessly (subject to the 160-bit requirement of my dsa key). Symmetric encryption works as it should (regardless of the s2k setting in gpg.conf) with my 1.2.6 installation. I have not tested earlier 1.3.x releases.

Fix

Unknown

Event Timeline

ldjpearson added projects: gnupg, Bug Report.Dec 15 2004, 10:55 PM
dshaw closed this task as Resolved.Dec 16 2004, 12:16 AM
dshaw added a subscriber: dshaw.

This is correct behavior. Use --s2k-digest to set the S2K
digest for both symmetric and asymmetric encryption.
--digest-algo is not meaningful for -c/--symmetric unless
you are using --symmetric --sign to make a signed symmetric
message.

This is different than 1.2.x, where --s2k-digest was used to
specify the S2K for asymmetric, and --digest-algo was used
to specify the S2K for symmetric.