A client delivers data to us from an IBM zOS mainframe, encrypted via "Megacryption", a commercial
product which supports the OpenPGP standard. As such, the contents of the files, once decrypted, are in
EBCDIC. We're running on an AIX 5.3 box.
When decrypting the latest batch (about 70) of files, some files produce no [don't know] messages, some
produce multiple [don't know] messages, some produce messages which look fatal... however SHA1'ing the
decrypted file against the SHA1 digests produced by the client shows me that the data has been decrypted
OK!
I'm have a logfile of the output produced, showing a wide and varied selection of "issues" but I don't
want to attach it to a public bug due to client confidentiality. Happy to mail to someone privately
however.
A quick example with some parts redacted:
[redacted] is being decrypted at Wed Jun 1 11:35:23 BST 2011
gpg: WARNING: using insecure memory!
gpg: please see http://www.gnupg.org/faq.html for more information
gpg: armor header: Version: MegaCryption/MVS v6.2 http://www.aspg.com
gpg: public key is 8ABFF8CF
gpg: NOTE: signature key D0CD7FC5 expired Mon Aug 9 13:35:44 2010 BST
gpg: NOTE: signature key D0CD7FC5 expired Mon Aug 9 13:35:44 2010 BST
gpg: NOTE: signature key D0CD7FC5 expired Mon Aug 9 13:35:44 2010 BST
gpg: using subkey 8ABFF8CF instead of primary key D0CD7FC5
You need a passphrase to unlock the secret key for
user: "Userid (Valid for 6 months only) <some.user@example.com>"
gpg: NOTE: signature key D0CD7FC5 expired Mon Aug 9 13:35:44 2010 BST
gpg: using subkey 8ABFF8CF instead of primary key D0CD7FC5
2048-bit RSA key, ID 8ABFF8CF, created 2010-02-10 (main key ID D0CD7FC5)
gpg: NOTE: signature key D0CD7FC5 expired Mon Aug 9 13:35:44 2010 BST
gpg: NOTE: secret key 8ABFF8CF expired at Mon Aug 9 13:35:44 2010 BST
gpg: encrypted with 2048-bit RSA key, ID 8ABFF8CF, created 2010-02-10
"Userid (Valid for 6 months only) <some.user@example.com>"
gpg: AES256 encrypted data
gpg: original file name='[redacted]'
gpg: [don't know]: invalid packet (ctb=04)
gpg: WARNING: message was not integrity protected
gpg: original file name='½+°B~$öiaÚ¦¼²lN÷ÿæò´¶HÉNG oVúËæò´¶HÉNG oVúËæò´¶HÉNG
oVúÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ'
gpg: WARNING: multiple plaintexts seen
gpg: handle plaintext failed: unexpected data
I don't know if this is a problem with the method of encryption, how I'm decrypting, if it's the data
coming from an EBCDIC machine which is throwing things out, etc... The fact that I see messages like the
above, and yet seem to get valid data decrypted anyway has me puzzled but not overly concerned!
Anyone interested in working out what's going on?