Bug#813726: claws-mail-pgpmime: Can't encrypt if one of the recipient keys has MD5 digest algo specified
control: tags -1 moreinfo Hi Norbert, On Thu, Feb 04, 2016 at 07:27:35PM +0100, Norbert Bollow wrote: > Package: claws-mail-pgpmime > Version: 3.11.1-3+deb8u1 > Severity: important > > Dear Maintainer, > > Encrypting email fails with the error message "Couldn't encrypt the email: > Encryption failed, General error" if one of the recipient keys specifies > the MD5 digest algorithm. Just tried "gpg --version" and "gpg2 --version" and both have MD5 available as digest algorithms (Debian 8.3). > I have found that putting "allow-weak-digest-algos" in my ~/.gnupg/options > is an effective work-around as far as encryption from claws-mail is concerned. > > However, adding that option causes encryption and decryption with gpg from > the command line to break (error: "invalid option"), so that is not an > acceptable work-around overall. Which one does break gpg or gpg2? By default ~/.gnupg/options is ignored, should be ~/.gnupg/gpg.conf¹, so don't really understand what's the problem. Can you run claws-mail with --debug option in a terminal and try to encrypt a mail to one of those recipients? It may show more info on what's happening. thanks in advance, ¹ https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration.html -- Ricardo Mones ~ Absence of evidence is not evidence of absence. Carl Sagan signature.asc Description: Digital signature
Bug#813726: claws-mail-pgpmime: Can't encrypt if one of the recipient keys has MD5 digest algo specified
Package: claws-mail-pgpmime Version: 3.11.1-3+deb8u1 Severity: important Dear Maintainer, Encrypting email fails with the error message "Couldn't encrypt the email: Encryption failed, General error" if one of the recipient keys specifies the MD5 digest algorithm. I have found that putting "allow-weak-digest-algos" in my ~/.gnupg/options is an effective work-around as far as encryption from claws-mail is concerned. However, adding that option causes encryption and decryption with gpg from the command line to break (error: "invalid option"), so that is not an acceptable work-around overall. Greetings, Norbert -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages claws-mail-pgpmime depends on: ii claws-mail 3.11.1-3+deb8u1 ii libarchive13 3.1.2-11 ii libassuan0 2.1.2-2 ii libatk1.0-0 2.14.0-1 ii libc62.19-18+deb8u2 ii libcairo21.14.0-2.1 ii libdb5.3 5.3.28-9 ii libenchant1c2a 1.6.0-10.1 ii libetpan17 1.5-2 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-3+deb8u1 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u4 ii libglib2.0-0 2.42.1-1 ii libgnutls-deb0-283.3.8-6+deb8u3 ii libgpg-error01.17-3 ii libgpgme11 1.5.1-6 ii libgtk2.0-0 2.24.25-3 ii liblockfile1 1.09-6 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpangoft2-1.0-01.36.8-3 ii libsasl2-2 2.1.26.dfsg1-13+deb8u1 ii pinentry-gtk20.8.3-2 ii zlib1g 1:1.2.8.dfsg-2+b1 claws-mail-pgpmime recommends no packages. Versions of packages claws-mail-pgpmime suggests: ii gnupg-agent 2.0.26-6 -- no debconf information
