> > It's signed. Just pipe it through gpg with Keiths public key.
> Signed means that there is a checksum at the bottom that you can
> verify with gpg/pgp to see if the message was tampered with, but the
> text itself it still in ascii and not encoded.
Not that it matters (he did send out a reprint) but the message *was*
merely signed. The base64-looking encoding is merely a way to make
sure that MTAs and other software don't screw with tabs, line breaks,
etc., which would make the signature look invalid.
> This looks encrypted to me.
It doesn't look encrypted to gpg. Pipe the message to it, you'll see.
kbuild-devel mailing list