ascii armor

[Anthony E. Greene]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 24 Oct 2001, Brian Minton wrote:
>On Tue, Oct 23, 2001 at 06:23:17PM -0400, David Shaw wrote:
>> gpg --enarmor
>
>which produced a file that was
>1) completely different from when I used mimencode (ok, this turned out not
>to be true, the characters were the same, there were just a different number
>of characters per line, no problem) and 2) used the Armor Header Line
>"-----BEGIN PGP ARMORED FILE-----" instead of the RFC's reccomendation of
>"-----BEGIN PGP MESSAGE-----" (the binary message was in fact already
>encrypted, so this is the right choice...)
>
>on a side note, this command is not mentioned in the gnupg "info"
>documentation, niether is the --dump-options command that I could have used
>to learn about it

It is listed in "gpg --help".

- -- 
Anthony E. Greene <agreene@pobox.com> <http://www.pobox.com/~agreene/>
PGP Key: 0x6C94239D/7B3D BD7D 7D91 1B44 BA26  C484 A42A 60DD 6C94 239D
Chat:  AOL/Yahoo: TonyG05
Linux. The choice of a GNU Generation. <http://www.linux.org/>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Anthony E. Greene <agreene@pobox.com> 0x6C94329D

iD8DBQE71nF2pCpg3WyUI50RApJfAKCOTo/RFLTfNSwKCcmFypQ9Io64oACg7ksQ
7Ky3jI8mEbRbSBsOTV0lXMk=
=xS0u
-----END PGP SIGNATURE-----