From 43ea1d8ae931cfafe9a921c71e40c1a2c13804701d3166ce16c4778a02b4e07b Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Fri, 29 Apr 2022 00:00:00 +0000 Subject: Change post to entry --- content/post/statement-of-gpg-key-transition.md | 35 ------------------------- 1 file changed, 35 deletions(-) delete mode 100644 content/post/statement-of-gpg-key-transition.md (limited to 'content/post/statement-of-gpg-key-transition.md') diff --git a/content/post/statement-of-gpg-key-transition.md b/content/post/statement-of-gpg-key-transition.md deleted file mode 100644 index d244ac6..0000000 --- a/content/post/statement-of-gpg-key-transition.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -title: "Statement of GPG Key Transition" -date: 2021-12-30T00:00:00 -draft: false ---- -Date: 2021-12-30 - -Statement of GPG Key Transition - -To replace my GnuPG key, I have set up a new Signify key, and will be transitioning away from my GnuPG key. - -The GnuPG key will continue to be valid until 2022-02-01 for the purpose of verifying this transition statement. Please do not use it send me encrypted emails anymore. - -This message is signed by both keys to certify the transition. - -The old GnuPG key's primary key fingerprint was: -BF49E81C1D888979B6506B225B4FE8CA89C066C0 - -The new Signify key is: -RWTJ8JZMFWhB2Ya9GyXbmOQKSxd/x57IV/oNo6/nl344CR1aqf/OgPXf - -If you have my old GnuPG key, you can verify this transition statement with: -gpg2 --verify gpg-signify-transition-statement.txt.asc - -You can verify the new Signify key with: -signify -V -e -p key.pub -m gpg-signify-transition-statement.txt - -Thank you, and sorry for the inconvenience. - -Nick - - -Link(s): -[gpg-signify-transition-statement.txt.asc](../../../../resource/gpg-signify-transition-statement.txt.asc) -[gpg-signify-transition-statement.txt.sig](../../../../resource/gpg-signify-transition-statement.txt.sig) -- cgit v1.2.3