Here’s a signed message about my GPG key update
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
So last year, during 33c3, I wrote about how I was making a new GPG key and hoped to use it more. I’m not going to look at how well it worked, because that wouldn’t be such a good look for GPG usage (it’s mainly been used in git commits. I’ve receiveda grand total of… 2 emails during the year that were GPG encrypted).
Anyway, back then I set it to expire after a year. I followed this
post on how to make it
back then, and I followed that same post on how to make it this time, only
--edit-keying the key to change the expiration date and posting the public key
on keyservers afterwards.
I’ll be at 34c3 this year, so if you’d like to do a bit of keysigning with me hmu using twitter or mastodon (or via email, or directly there, or any other way I guess). I’ve also made a tweet here and a toot here to prove my authenticity too.
Either way, hope too see yall at 34c3 and that you have a good time over the holidays! 😄🎄🚀
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEZDroKcxTGuCO4MGxjYC/gJdzRz8FAlo/+34ACgkQjYC/gJdz Rz9C5BAApSLcBTL3tpt6UZDcsX/RpqD3Lozx5QUT7pSCc89B8eebdBfSff9LKwgr AKPhNxgSyCwomknRKazTQDYks7fSVXw0wQVeyQFlidgl5B1+IbqPu87ko3vCyERm EH1N9JH2fOR/ZUeBoFwZUJp9NP92qMRaZrxFvxkhjgyV+OwRiOkTh/DxMWy4KAkP PIzwEDUM37GtdFHj2hFSCDLqAHN4mHMbRJbbbqCnlfc7sppkaqltbOQF6jNFkpo1 Gm/AawJV57l8YYPtj8LoL3aCGZ4ebst6oZeE+e0m5ap7hw36/+2QxKcOGf93R9Cr zWW8cdUy5Ky07zT3+oRBHqPXSYbCFeR9yYhyFc9dRRcYfrsp0xCgce6yNl6D+pl6 b6dzOBeitTkahf4s6hKKhGaHqyVxm8Oj67u2txUu40qF7Dz+lEvXMaOjJZVRcp2K SaaZ4we51y2CYoYPw4NlYyPhaCJcnVQxZhSeYFFgDs26Mo2GZICB0FD1SF9hrM5B sMhOiMmo4XAu5cDJVpQOa5AUdmwdaffpo46PBnV6AG4oRfOX9nOSmYc/9k5yZW29 YtbODD9/eSn++YGd/6q5AXjKwy80bQUKCZb/Fph+h+OHjcY9dp2mKXoDmFaly/HU Gy1KnuBlVteDNIK26ygAMCRKcwEWmxfRK43EWNsI+rxMdwpLwIQ= =NvZ6 -----END PGP SIGNATURE-----
I’ll also make this message available on here so that if copy-and-paste gpg verification doesn’t work at least you can do it with a plaintext equivalent.