Bug with GnuPG 2.1.1 on Windows 7 x64

[Robert J. Hansen]

> Can you move the private keys away from the OS X box and try again? 

Same results as on Win7/x64.  *However*... I have some useful
information.  Namely, I mistyped the passphrase and got the output below:


quorra:~ rjh$ gpg -vvvv backup.tar.xz.gpg
gpg: using character set 'utf-8'
# off=0 ctb=85 tag=1 hlen=3 plen=526
:pubkey enc packet: version 3, algo 16, keyid B8A6B74C001892C2
	data: [2044 bits]
	data: [2047 bits]
gpg: public key is 001892C2
gpg: no running gpg-agent - starting '/usr/local/gnupg-2.1/bin/gpg-agent'
gpg: waiting for the agent to come up ... (5s)
gpg: connection to agent established
# off=529 ctb=85 tag=1 hlen=3 plen=268
:pubkey enc packet: version 3, algo 1, keyid E5B12DCFA1AC6FC0
	data: [2047 bits]
gpg: public key is A1AC6FC0
# off=800 ctb=8c tag=3 hlen=2 plen=46
:symkey enc packet: version 4, cipher 2, s2k 3, hash 2, seskey 256 bits
	salt 018490B8887579F9, count 65536 (96)
gpg: 3DES encrypted session key
# off=848 ctb=d2 tag=18 hlen=2 plen=0 partial new-ctb
:encrypted data packet:
	length: unknown
	mdc_method: 2
gpg: encrypted with 1 passphrase
gpg: using subkey A1AC6FC0 instead of primary key 2B89BD45
gpg: encrypted with 2048-bit RSA key, ID A1AC6FC0, created 2011-07-28
      "Robert J. Hansen <rjh at sixdemonbag.org>"
gpg: using subkey 001892C2 instead of primary key D6B98E10
gpg: encrypted with 2048-bit ELG key, ID 001892C2, created 2008-07-30
      "Robert J. Hansen <rob at enigmail.net>"
gpg: encrypted with unknown algorithm 64
gpg: decryption failed: Invalid cipher algorithm


... but when I entered the passphrase correctly, it decrypted correctly.
 I suspect I mistyped the passphrase on Win 7/x64; I'll check that in
the morning.

Still, GnuPG reporting an invalid cipher algorithm when the real problem
is a bad passphrase should still be a bug worth fixing.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3744 bytes
Desc: S/MIME Cryptographic Signature
URL: </pipermail/attachments/20150113/ba9c6da8/attachment-0001.bin>