[PGP-USERS] Re: ascii armor

[David Shaw]

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

On Wed, Oct 24, 2001 at 12:15:39AM -0500, Brian Minton wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> On Tue, Oct 23, 2001 at 06:23:17PM -0400, David Shaw wrote:
> > gpg --enarmor

> 2) used the Armor Header Line=20
> "-----BEGIN PGP ARMORED FILE-----" instead of the RFC's reccomendation of=
=20
> "-----BEGIN PGP MESSAGE-----" (the binary message was in fact already
> encrypted, so this is the right choice...)

So change the header :)

You asked for a tool that will change a binary format PGP message into
an ascii-armored version without changing the binary.  The armored
file that --enarmor generates works fine with both GnuPG and PGP 6.5.8
(the only one I have handy to test with).

cat my_file | gpg --enarmor | sed -e 's/ARMORED FILE/MESSAGE/'

David

--=20
   David Shaw  |  dshaw@jabberwocky.com  |  WWW http://www.jabberwocky.com/
+--------------------------------------------------------------------------=
-+
   "There are two major products that come out of Berkeley: LSD and UNIX.
      We don't believe this to be a coincidence." - Jeremy S. Anderson

--7AUc2qLy4jB3hD7Z
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iQEVAwUBO9a4JIccwqs8s7QVAQG6ygf/XmAfHw5yWAHt85zj8O0zPN28VadZgit7
V7/JxxAihk+FXrqg0oBoAJpfMCX/ucDy/I8OJ3HpTiPrNPAN99bQFdF4Q63IkDQ9
4x2e4hQgsrA6SDAtQ6HvaIwOQ3j1CS7TwXj7FUlN8EEKh6ZlD+2ZXozkV85OXwfS
X0suwTNlu+H7tvA6DqXdhPCIzdNR4u+NPuJQkfXpaS41ZpvUDg6BrnIvueR8dZWk
TkhPC2l5dQg4MGwS4LAIMmeWmaqhnpMMcV1+X9SXnzLvy9/Y5fvw96dEB3dpc7HF
JCRF+92KHCiEEVKSXcHcGXPgHd/NwrKKCCudz/tq3i578G7El+BZww==
=D8zn
-----END PGP SIGNATURE-----

--7AUc2qLy4jB3hD7Z--