Cannot encrypt/decrypt zip-Files correctly (Andreas)

[David T-G]

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

Steve, et al --

=2E..and then Steve Butler said...
%=20
% I missed the -a flag on the first read.  So, the encrypted file could be
% ftp'ed as ASCII as the -a does give the ASCII armoring.

It looks like a lot of us did :-)


=2E..
% But, I can think of some reasons why that might be desirable (disregarding
% any side affects of attempting to compress an already compressed file).
=2E..
% PS  None of the "desirable" reasons will hold water for a purist.

Oh, I can think of some that might be...  Since he's encrypting the file
on the system before transmission, we might safely assume that the file
lives on the system and only needs to be encrypted when sent over the
'net.  In that case, one would certainly want the file to take up as
little space as possible on the disk, or at least you would if you're
a pack rat like I am.  If you're worried about the extra time, you can
just add a "-z 0" flag and away you go without any waste.

While I can think of few reasons for compressing before encrypting as a
part of the process (maybe there isn't much disk space on the receiving
end, though), having a file already compressed makes sense in lots of
ways.  Opinions?


TIA & HAND

:-D
--=20
David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE8/S96Gb7uCXufRwARAkdKAJ0Z4XSXnnXRfeXU1onu3ZP1o3gLFgCg1Qbn
1Mo1IRSM5SBFa3YnWU7xE20=
=0hPX
-----END PGP SIGNATURE-----

--ZrCu0B0FMx3UnjE2--