Error decrypting after upgrading gpg (Windows)

[Öberg Fredrik]

Hi,
After upgrading from 1.2.2. to 2.0.30 we have problems decrypting files from our partner

C:\Temp\GnuPGtemp>gpg --version
gpg (GnuPG) 2.0.30 (Gpg4win 2.3.3)
libgcrypt 1.6.6
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: C:/Users/UsrFoo/AppData/Roaming/gnupg
Supported algorithms:
Pubkey: RSA, RSA, RSA, ELG, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

Decrypting with

C:\Temp\GnuPGtemp>gpg -vv -o 401611390.170302.txt -d 401611390.170302

results in this:
----
:pubkey enc packet: version 3, algo 16, keyid [keyid]
        data: [2048 bits]
        data: [2048 bits]
gpg: public key is [subkey]
gpg: using subkey [subkey] instead of primary key [primarykey]

You need a passphrase to unlock the secret key for
user: "[my organization]"
gpg: using subkey [subkey] instead of primary key [primarykey]
2048-bit ELG key, ID [subkey], created 2009-09-16 (main key ID [primarykey])

gpg: public key encrypted data: good DEK
:encrypted data packet:
        length: unknown
gpg: encrypted with 2048-bit ELG key, ID [subkey], created 2009-09-16
      "[my organization]"
gpg: 3DES encrypted data
:literal data packet:
        mode ? (A0), created 2927189294, name="\xb7\x0adR\xde\xd6\xed\x09A&\x11\x0do_\x14\xf2\x0b\xab%\xfa\x96\xdd\xf7\xcd1\x82\xc
d\xed\x0c\x89F,_z\xcd_\xd9\xb0\xbaaZ\x9e\x9f`\xaf\xc8\xcb\x9b",
        raw data: 2369445039 bytes
gpg: original file name='À
o_¶‗♂½%·û¦¸═1é═Ý♀ëF,_z═_┘░║aZ׃`»╚╦ø'
gpg: problem reading source (2369443780 bytes remaining)
gpg: handle plaintext failed: No such file or directory
gpg: decryption okay
gpg: WARNING: message was not integrity protected
---
The decrypted file contains just jibberish.

If I decrypt the same file with the ancient gpg 1.2.2 everything works fine.

Our partner tells us they encrypt the file with gpg version 1.2.1 using the command

gpg -e -c 3DES -r [our key]

Nothing has changed there since 2011.

Any ideas why it is fine to decrypt using 1.2.2 but not using 2.0.13?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20170419/495e0d8b/attachment-0001.html>