ascii armor

[Brian Minton]

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

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

- -- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
http://cs.smsu.edu/~minton / PGP key id 0x24B44202     _    _my favorite OS!
bjm918s@mail.smsu.edu     / www.bellview.org          | |  <_>._ _  _ _ __
bminton@earthling.net    / What are you waiting for,  | |_ | || ' || | |\ \/
bminton@efn.org         / try Jesus today!!!          |___||_||_|_|`___|/\_\
"Many shall run to and fro, and knowledge shall be increased"  --Daniel 12:4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE71k3vp0PPDCS0QgIRAu3bAJ4gudmYscXfSK4DGpHX+JgzFBOMugCfbmFM
wmfNHf/V4jSCgkMtVL1d2T8=
=WmrY
-----END PGP SIGNATURE-----