Strange problem with GnuPG 1.0.4 encrypted data

[LO Richard]

Thanks for your reply.

1. I did a "od -x" dump of the gpg file and there are a lot of "0x14" value.
How do I check which byte is the spurious one ? 

2. about the ">Last Night a file was transferred which appeared .......",
I just quote someone's message from last month.

3. I run gpg -vv from both gnupg 1.0.4 and 1.0.6, the following is the
output :

GNUPG 1.0.4 
############################# start ###############################
$ gpg -vv input.txt.gpg
gpg: Warning: using insecure memory!
:pubkey enc packet: version 3, algo 16, keyid 0BB441B5515D6806
	data: [2047 bits]
	data: [2048 bits]
gpg: public key is 515D6806
gpg: loaded digest 2
gpg: using secondary key 515D6806 instead of primary key 4752373C

You need a passphrase to unlock the secret key for
user: "GPGkey"
gpg: using secondary key 515D6806 instead of primary key 4752373C
2048-bit ELG-E key, ID 515D6806, created 2001-10-24 (main key ID 4752373C)

gpg: key 4752373C: accepted as trusted key.
gpg: public key encrypted data: good DEK
:encrypted data packet:
	length: unknown
	mdc_method: 2
gpg: encrypted with 2048-bit ELG-E key, ID 515D6806, created 2001-10-24
      "GPGkey"
gpg: RIJNDAEL encrypted data
:compressed packet: algo=2
:onepass_sig packet: keyid B98DC05352497C82
	version 3, sigclass 00, digest 2, pubkey 17, last=1
:literal data packet:
	mode b, created 1006742195, name="input.txt",
	raw data: 12195 bytes
gpg: original file name='input.txt'
:signature packet: algo 17, keyid B98DC05352497C82
	version 4, created 1006742195, md5len 0, sigclass 00
	digest algo 2, begin of digest 62 a5
	hashed subpkt 2 len 5 (sig created 2001-11-26)
	subpkt 16 len 9 (issuer key ID B98DC05352497C82)
	data: [158 bits]
	data: [160 bits]
gpg: Signature made Mon 26 Nov 2001 01:36:35 PM EST using DSA key ID
52497C82
gpg: Good signature from "ABC"
gpg: [don't know]: invalid packet (ctb=14)
gpg: decryption okay
############################# end ###############################


When I run gpg 1.0.4, I got the same result except the difference is 

	:
	:
gpg: [don't know]: invalid packet (ctb=14) near 2601
	:


I would like to bypass this particular problem if the data is decrypted
properly, 
however, there is no specified return value returned from gpg. It's return
value 
for this problem is (2) which is a general error. Is there any way to get
around it ?

Thanks for your help.









IMPORTANT NOTICE:
This e-mail and any attachment to it is intended only to be read or used by
the named addressee.  It is confidential and may contain legally privileged
information.  No confidentiality or privilege is waived or lost by any
mistaken transmission to you.  If you receive this e-mail in error, please
immediately delete it from your system and notify the sender.  You must not
disclose, copy or use any part of this e-mail if you are not the intended
recipient.  The RTA is not responsible for any unauthorised alterations to
this e-mail or attachment to it.