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

[Ricardo SIGNES]

--xHFwDpU9dbj6ez1V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Jan 28, 2002 at 08:27:29PM +0100, Janusz A. Urbanowicz wrote:
> Steve Butler wrote/napisa?[a]/schrieb:
> [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > We have a client who routinely sends us an encrypted file using the ASC=
II
> > rather than BIN ftp format.  At least whenever we have had them resend =
it
> > ...
> > Has anybody played with doing a post-FTP fixup of such a file?  Suggest=
ions
> > 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.

I agree with Alex.  Once that 8th bit is gone, it's gone.  There's no
parity.

--=20
rjbs

--xHFwDpU9dbj6ez1V
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjxVs2EACgkQDIxbLaZ099MoEQCfR9umEM/0DE8qXISiirsCtoGJ
HLkAoIueLcief6nJlZ8DnOQ+ycuIEs9u
=4vy0
-----END PGP SIGNATURE-----

--xHFwDpU9dbj6ez1V--