I prefer all private mail being encrypted.
My GnuPG public key's fingerprint (and from the keyserver) should read
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
pub 4096R/0x6A6CD5B765632D3A 2013-01-10
Key fingerprint = 2265 D7F3 A7B0 95CC 3918 630B 6A6C D5B7 6563 2D3A
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCAAGBQJUu/MgAAoJEGps1bdlYy06nAQP/1+FObMYbH74D8EjxYdcAHiL
xq51FyjYg7E07m0yAbyGHB8rlytMRHbaQBe3vSy6YmkD4Oo95Kuda4qH4Nsra7Nu
QoZfM0NwePk2wgUtPdJAyStUFoqBoEOAuokEsFWR8k2sdVLVygj8crD93nQ3uDDF
F6uPsb28Khrpnzc5iI+8XZn679mcY9uJGHv4hrAyRJcbkbFAkzOcO++XMhhvA9hi
ulQ9K/A75MxM5RogJ5lUdvuppcXZhMlqdovaVWl2gfsUEQ89WpJ/GAexBLOBuyVm
Zy2RuQx7VtBUW3OLERiFyyldFsXT+IVsp9oMxt4HGv9lsItRm3cA+fg9mkeHrihV
J1F9qoqf9in4Oe6Xak88hLmWn4f9SLtKfDORkbKqBjVWr2YLpEWOtqZpTdAH6tj0
W/7brR0rVYL5MXiQM2dodpKhKVBHdJN8oXJx54MpCC4NeouN3wdqT9IUggKtrbtk
GZEm7HMB0QXC55+QtaNiOrTt7lkvJhYl+wfsKdiH4YwxmX5WitzSLtd920Y5PQO8
TEejodZKVaYX202GZY+qjyssrydo1qjrKMMERf0JP50hMbYsRFjtjCyLe5ZH8SYS
hY5tkWJCWBP/ope2jz2cDncPuHA5USPfhZeaq4aBRTDc5FhIWnrU2sMt0fjsd/VD
DtHrC47VNr9/RvHN0fRI
=M08i
-----END PGP SIGNATURE-----
If you already obtained my key you may verify the signed section above by feeding it to the gpg --verify command, for example via clipboard/stdin.
Note that for the key ID the 64 bit long format 0x6A6CD5B765632D3A produced by the --keyid-format 0xlong option is used, in your environment you may see the 32 bit short format 0x65632D3A produced by the implied default --keyid-format 0xshort that should be avoided.
This key can also be retrieved automatically by Web Key Directory (WKD, see below) supporting email clients for the @erack.de email addresses, note however that due to size (as a user wants a fast download for writing a mail) those WKD keys are exported minimalized without all external signatures (gpg --export --export-options export-minimal ...).
The key is also available from the new (since 2019-06-12) keys.openpgp.org keyserver that verifies email addresses associated with uids before publishing them.
The key replaces my previous
key 0x2F1AD073293C05FD (0x293C05FD)
If you are interested in details of the key transition please see the document
key-transition-2013-01-10.txt.asc
that is signed with both keys.
My Keyoxide profile and keyoxide-blue (fully client-side, experimental, may or may not work).
My Keybase.io account and index.
verbose index for my GnuPG key (and for my previous GnuPG key and my ancient PGP RSA key)
Warning: someone "funny" uploaded a key 0xEF283C2E0EC89145 (0x0EC89145)
fingerprint = 9499 D4CE BD6C FA60 46A0 4F4D EF28 3C2E 0EC8 9145to the servers that is not my key. Encrypting to that key will enable someone else to read the message. I won't be able to decrypt anything encrypted to that key, nor is anything signed by that key written by me!
The same for key 0x4B4B8E1CDA620A55 (0xDA620A55)
fingerprint = 9B59 602A 758D F7E4 E5FF B67C 4B4B 8E1C DA62 0A55which is a fake of my ancient 0x79168F91DA620A55 key.
If you don't have an OpenPGP capable mail user agent, you may encrypt a message to my key using tencrypt that runs in your browser, if you trust it enough. You'd have to copy the result and paste it into your mail's body (or wherever).
gpg --export --export-options export-dane [email protected]
Home ../../bookmarks