GnuPG AO messages

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

Going to start GnuPG signing all of my messages posted here at AO lol.

Just for shits and giggles, but if it ends up being annoying, just say the word.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32) - WinPT 0.9.90-rc1

iD8DBQFCHsoHyTlseSg5nqsRAjnEAJ90KbItbMVNdiHXgAQp7PWLOSnbLgCgnXEV
Kx0kye1o6XUv28o9jzsbRnY=
=1wje
-----END PGP SIGNATURE-----

Not that i care much but WHY ?

Im sure its gonna become annoying and yeah why !?!

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

Yeah man, this is kinda a pain in the arse. Heheh.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32) - WinPT 0.5.13

iEYEARECAAYFAkIfh4UACgkQbIIo8a0Jc4msVwCbByCM11IjWg0sRQ9rabBPJrSL
4eUAn2OHbZxQ0ynorjIMoWC2OxyvnUTx
=VP9/
-----END PGP SIGNATURE-----

Is AO messing up the PGP syntax? I can't get your posts to verify...

Well.... do you have our public keys?

I think I have yours, GA... unless you are using a new one. I don't have TH's. The error I'm getting is a ascii armor input incomplete dialog.

Here's my public key... from www.keyserver.com

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: FileCrypt KeyServer 1.0

mQGiBD4Z8KARBADMs+ElXCClpLRTYCL4Thyp6tn0QNQat/TjFmEMV5Qg/opju1ca
NQXsGVXRfpZC+QuJ5Pu2JVey8poJr2wmQ3Jaym3WCjMPrG0r7t1WSdetcCIACe+/
7/IM6kixMKMYbloDEN/ZaCaJ75mK9TZy//eKhL14nao9rVOANEIDzI1I9wCgy3aJ
52bC5DZFQUo4FnVQvzGM/NkEAKZrpAmB28E7cOjjC7V0ewd+1ZsxNEX9I00LvJtb
H7Hs4Qb+sPFg+PjZFXOrhy+cEPiZP5rCSjp2mYY3t+UfVF41xEXU+/tMVw5/tO7R
lPN9LvxITncYFD6F6LIi9fC3jsH89l89iNJ+EYQJphgO1gA6Kxz7LWgfrhrlqN+b
g3+pA/0fpiDPHUSAVAGTmX+9CNq3xJuG5ysykaWPxqfqOeRHb2+RQcb6OuIaAUTs
XtfQg56QL4mMbeJhGtkAgGrZvF05seyAXnVJpKcEPf17ia1qPvgsHuJi79l9tW9q
9UhFre3Ey8Kg/F78CmlP297GduAyuTHUQ0XaD25V1H5ne/HjAbQpU29ubnkgRGlz
Y2luaSA8c29ubnkuZGlzY2luaUBjby5tby5tZC51cz6IVwQTEQIAFwUCPhnwoAUL
BwoDBAMVAwIDFgIBAheAAAoJEGyCKPGtCXOJqL8AoJXTVfmc3qUXH6BXgMXXDorg
diKXAJ9SMnN435GFw0xcLKeON/HvCPsPFLkBjQQ+GfCkEAYAgyxrlt1lS68ySQys
Yoq/zHpSdESR/ri1KwS+Ii16aR/dGIw2w3lcnWEZZU9IvoawnB2ozF0S4J9l2J/6
ialN9CdCJfYAZNw5dxhoFicSpGTxtOZ6k37vOWJpMf2a0obeTBXocRFUNmcIv2Ut
8SAqGjF+BqO+AM1STvbDg6bmtoJMkyxNj6vUcZcqlC1hBox9zsaJgPZWMiEd/mxi
1QC1v+6ASRAJiBhvGlO0DRPSHqszSg+M2E4ibBhP01VdH0lnAAMHBf9mzuFoyLQt
EPIv0PqDbIdmt8L5wOMgIfYY8mAV3rh5k9zMRCJzeukydJARPVWfKGtkgYWFENUu
I0rue/lyWGnE87GhpPR0Fmczd0fBrv+HbHJMBnOJhHHUFKcYtnl3VEFZJ5zQd1ye
zVx0rli8GYQ6qU5sCBmdisqCOR6q1NZNX9v59KKcAZOvb4bskJbQEfWCDvxsMona
jJLNCsUCIMh0WBtzK7D6fO24NNhCgihf6DurP6n+T/NAa4ASSNYg8UmIRgQYEQIA
BgUCPhnwpAAKCRBsgijxrQlziS7kAKCUTqPAzPU/T6hvscS6QVr6lblufwCffAin
gCmqm5Dz9lBy8QOV9SiNOhs=
=IQV1
-----END PGP PUBLIC KEY BLOCK-----

soda now that you have my public key, does it verify?

Nope, I still get ascii armor errors with PGP freeware 8.1. I'm guessing it's an antionline thing.