Yakman
2009-08-24 00:24:10
lets all post our gpg public keys here.
A Short Introduction
gpg is software which handles public-key cryptography. This works by having keys, each person has a private key which they keep secret, and a public key which they spread around.
Suppose Alice wants to send an encrypted message to Bob, she encrypts her message with Bob's public key. Only Bob can decrypt it because only Bob knows his private key.
There is also a feature called digital signatures. This is a way of mathematically proving that a message came from that sender and that it hasnt been modified in transit.
Suppose Alice wants to send a message to Bob and be sure that no-one else has modified it along the way. She signs her message with her private key and Bob can verify it with her public key. Only Alice can sign because only she has her private key, but anyone can verify because anyone has her public key.
For this to work, you need to have the public key of everyone you're communicating with, hence this thread.
It asks for your real name, but I've only put yakman for the purposes of SRL.
Why am I doing this?
for a bit of fun, and it might come in useful.
I'll start, this is mine.
I've signed a message here to show you what its all about.
Almost all linux distros come with gpg already installed, if you're lucky, you may have a graphical front end such as kgpg or seahorse.
If not, you can use these steps on the terminal to generate you own key pair.
edit: here are also some command line flags for doing common tasks
digitally sign file "cleartext"
verify digital signature file "cleartext.asc"
encrypt file "cleartext" with the public key of "yakman"
decrypt file "cleartext.asc"
Whenever you send an encrypted message to someone, it should be signed too. If you dont, it opens up a variaty of cryptoanalysis attacks.
encrypt file "cleartext" with the public key "yakman", sign it and store in file "ciphertext"
if you receive a message like this, a combined verification of the signature and decryption
A Short Introduction
gpg is software which handles public-key cryptography. This works by having keys, each person has a private key which they keep secret, and a public key which they spread around.
Suppose Alice wants to send an encrypted message to Bob, she encrypts her message with Bob's public key. Only Bob can decrypt it because only Bob knows his private key.
There is also a feature called digital signatures. This is a way of mathematically proving that a message came from that sender and that it hasnt been modified in transit.
Suppose Alice wants to send a message to Bob and be sure that no-one else has modified it along the way. She signs her message with her private key and Bob can verify it with her public key. Only Alice can sign because only she has her private key, but anyone can verify because anyone has her public key.
For this to work, you need to have the public key of everyone you're communicating with, hence this thread.
It asks for your real name, but I've only put yakman for the purposes of SRL.
Why am I doing this?
for a bit of fun, and it might come in useful.
I'll start, this is mine.
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.9 (GNU/Linux)
mQGiBEqRrl0RBADrG4QyKfUa3Ju8gJ+6CTw/hkwB/mBkFN2EpinAMxMP7/lLmGmv
CR1LFINVOn6NOXKD49V5wfJChDJ5vN6yOHF8/KRxApKfXblHrF233U03pypqzNgx
bJQVlWgNNfaOQGi4kzodyxJtJownJWXEW1EW0DO6HhE0Ot1V1BD2XPB3LwCghGet
wSEV/PSDrcoKAGVz02uj4r0EALTlZijo+Et/bTsTNcXDVknF935FYFb8cpyLTX+D
zv/Qbyu7eCcZkpkz6BIs1zbrKoxq/RLTaLcncscblmMidz8GxwOMJoSqvU3Lg5hK
HLyJcPuXodglPfJFB1tVJStcXgjihg6DGft5VnFJRPKUPii4ylLp7h5mjxsPXG9f
qhX8A/9PEcRKKk+7GB86WaLd/A5NFrGsOlwIB7mOvOZKXtq3LjQ7zNmu4Q2Ur9bq
GjkPQMNJulld63h3yYRLE7BIiUYeP2lnDMzWiGX/gX2q8cnl61hCEJLU4ceQdQWC
riquzvC9W7jQEnaKk+jsZRIRMM3jUIMmoMhyEWKtj0CPLI4k2bQqeWFrbWFuICh5
YWttYW4ncyBzcmwga2V5KSA8ZmFrZUBlbWFpbC5jb20+iGAEExECACAFAkqRrl0C
GwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRC5cca+aLi26F/TAJ4uqxa0w5JG
XgFSzwrtZ13t6E+xZACcCAk2r0AgXowe7iIUelmqW5IvgZ25AQ0ESpGuXRAEALWe
pvTUedw83+ROqjuaXtqv8iedlMnPtcQRN4yCsnkfgvDySbzjFK3jtOwpsUMFWZvh
g0re818C2r+U81itAIzwUEchwLu83qFwinA32yIdzC3ylyy6Nds3kO8j+JXbeOzE
Unqwt5IyNwuCIsSFUeYDQDc0ch6owzslvdd0s1EvAAMFA/4wWINtNUw4DdaPw7YI
Y2mzGQf3K92xC9Jsnj+20NK0jm+B3ZAHsvvM+Q2kFKq/RuzJlCVLsYoA//Jy74mj
6Gm7bL5+6zDZw3HXRUYR4ce29/GxwHx+Y3ToLsL9cMEj8drmR20quVBy7GCTtEM0
CdY2HAwKBHcva+HAzhbSzPj3UIhJBBgRAgAJBQJKka5dAhsMAAoJELlxxr5ouLbo
/7kAn2kx9Ogkdrr+KXG9NI6w88gk8BFHAJ4+FkISAYRVgcJIxhig4eSoc+pWLg==
=F9nI
-----END PGP PUBLIC KEY BLOCK-----
I've signed a message here to show you what its all about.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello SRL
This message has been signed by yakman's private key, you can use his public key to verify that it really came from yakman.
Lots of love
yakman.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkqRsxEACgkQuXHGvmi4tuiA9QCfTf5hRFLBLSBMQqshAR+FuGll
SlwAn2eQK4IVxTxLC2b9IYSRIWEI7btL
=oSF+
-----END PGP SIGNATURE-----
Almost all linux distros come with gpg already installed, if you're lucky, you may have a graphical front end such as kgpg or seahorse.
If not, you can use these steps on the terminal to generate you own key pair.
$ gpg --gen-key
$ gpg -a --export your-name-here
edit: here are also some command line flags for doing common tasks
digitally sign file "cleartext"
gpg --clearsign cleartext
OR
gpg --clearsign < cleartext
verify digital signature file "cleartext.asc"
gpg --verify cleartext.asc
OR
gpg --verify < cleartext.asc
encrypt file "cleartext" with the public key of "yakman"
gpg -a -r yakman -e cleartext
decrypt file "cleartext.asc"
gpg -d cleartext.asc
Whenever you send an encrypted message to someone, it should be signed too. If you dont, it opens up a variaty of cryptoanalysis attacks.
encrypt file "cleartext" with the public key "yakman", sign it and store in file "ciphertext"
gpg -a -r yakman -e < cleartext | gpg --clearsign > ciphertext
if you receive a message like this, a combined verification of the signature and decryption
gpg -d ciphertext | gpg