ASCII versus BINARY ftp of encrypted file -- post ftp fixup?

JanuszA.Urbanowicz JanuszA.Urbanowicz
Mon Jan 28 20:36:01 2002

Steve Butler wrote/napisa=B3[a]/schrieb:
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> We have a client who routinely sends us an encrypted file using the ASCII
> rather than BIN ftp format.  At least whenever we have had them resend it
> using the BIN format the decryption works.  The error we get is:
> gpg: encrypted with 2048-bit ELG-E key, ID 5A2CEA48, created 2001-10-16
>       "First Choice Health Network (FCHN)"
> gpg: fatal: zlib inflate problem: invalid block type
> secmem usage: 2336/4128 bytes in 6/11 blocks of pool 4768/16384
> Has anybody played with doing a post-FTP fixup of such a file?  Suggestio=
> on how we might recover the file without having the sender ftp it again?

I don't think it is possible. Make him use ascii armor.

C _-=3D-_ H| Janusz A. Urbanowicz | ALEX3-RIPE | SF-F Framling |         | =
  *  =09
 ; (_O : +-------------------------------------------------------------+ --=
 ! &~) ? | P=B3yn=B1=E6 chc=EA na Wsch=F3d, za Suez, gdzie jest dobrem ka=
=BFde z=B3o | l_|/=09
A ~-=3D-~ O| Gdzie przykaza=F1 brak dziesi=EAciu, a pi=E6 mo=BFna a=BF po d=
no;     |   |  =20