Over the last few days I've seen a number of keys posted, both here on the forum and on SR vendor pages, of secret keys instead of public keys.This is very bad. The secret or private key should *never* be posted anywhere. As with the passphrase used to unlock it, it should be guarded and protected. If your secret key is available to anyone and you have set a weak passphrase on it then it is possible for the passphrase to be cracked. At that point you, along with anyone encrypting messages to you, are fucked.So when you are exporting your key, double-check that the key looks like this:-----BEGIN PGP PUBLIC KEY BLOCK-----Version: whateverComment: if you really need one(keyblock)-----END PGP PUBLIC KEY BLOCK-----Make sure that it absolutely does NOT look like this:-----BEGIN PGP PRIVATE KEY BLOCK-----Version: whateverComment: if you really need one(keyblock)-----END PGP PRIVATE KEY BLOCK-----I realise that the topic can be difficult to get your head around when starting with it, but it really is worth taking a little time out to do so.I also highly recommend reading this if you're new to OpenPGP, though it was written for PGP (the proprietary/original software):ftp://ftp.pgpi.org/pub/pgp/6.5/docs/english/IntroToCrypto.pdfThe PGP International (pgpi.org) site is a relic from the Crypto Wars, when PGP's source code was printed, flown to Europe, OCR scanned, compiled and released to the rest of the world because of America's munitions export laws (printed source code was classed as speech and protected by the First Amendment).