non ascii armor file sigs

[Jacob Perkins]

--=-sWezXhzvXF5MXpitsBLy
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


On Wed, 2002-12-11 at 11:00, Matthew Byng-Maddick wrote:
> On Wed, Dec 11, 2002 at 09:59:55AM -0600, Jacob Perkins wrote:
> > I'm using gpgme-0.3.14 (seahorse) to do the sigs, and it will verify
> > both fine.
>=20
> It occurs to me to wonder whether this is the problem, because
> your signatures to this list are currently coming up as "BAD".

I was just wondering why that is, but it is completely unrelated to
seahorse & gpgme since I'm using evolution 1.2.0 for email.  If anyone
knows why, please let me know.

Anyway, I just want to confirm this: gpg expects all armored files to
end in .asc, and non armored to end in .sig for signaturues or .gpg for
encrypted files?

--=20
Jacob Perkins <jap1@users.sourceforge.net>
seahorse

--=-sWezXhzvXF5MXpitsBLy
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

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

iD8DBQA994vQmq/Go6uOlQ4RAihBAJsEPUkbFcEf8UQ1HLo9JyfJUqDfQQCeKAYH
mkLr02VKg3wqKWTZmjNd6xY=
=Esjn
-----END PGP SIGNATURE-----

--=-sWezXhzvXF5MXpitsBLy--