Skip to content

Instantly share code, notes, and snippets.

@tarotene
Last active February 9, 2025 15:31
Show Gist options
  • Save tarotene/8df52f8411792ba9342a67a55c922846 to your computer and use it in GitHub Desktop.
Save tarotene/8df52f8411792ba9342a67a55c922846 to your computer and use it in GitHub Desktop.
Key Transition Statement #1

Key Transition Statement

I, tarotene, have been using two older GPG keys in the past:

  1. Old Key ID: 67FB9D4C05870F17

    • I no longer possess the private key or a valid revocation certificate.
    • Therefore, I cannot sign with this key nor formally revoke it.
    • It should be considered invalid and retired.
  2. Old Key ID: 13852C2BCB62BE66

    • I still possess the signing capability but have lost its revocation certificate.
    • I am therefore unable to fully revoke it in the usual manner.
    • I am issuing this statement, signed with this key, to declare it is no longer in use.

Both of these older keys should be treated as inactive and no longer trusted for any communication.

From now on, please use my new GPG key:

  • New Key ID: 6739E414B42965CA

I have signed the new key with the old key (13852C2BCB62BE66) to confirm that it belongs to the same owner. For the other old key (67FB9D4C05870F17), I cannot produce a signature due to the loss of the private key, but I include it here for completeness and to publicly state that it should also be considered invalid.

If you have any questions or concerns regarding this transition, please verify this statement by checking the signature from 13852C2BCB62BE66, or contact me through another trusted channel.

Thank you for your understanding.


Signed,
tarotene
2025-02-09

-----BEGIN PGP SIGNATURE-----
iHUEABYKAB0WIQT4gyESBRomF4czwEnD1whdKbj2cgUCZ6iikgAKCRDD1whdKbj2
cpMOAQDasNJGQwyRxjN1QczZjeDW93T+/VXTEBj0Of1aUhk4hgEA8ucrU2wcB8IX
3xGJ129ddq/03jMNCPAivwQZNr8SZgU=
=0Jqz
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
iLcEABMKAB0WIQTdAALqlHuxt9atUAsThSwry2K+ZgUCZ6iiHgAKCRAThSwry2K+
Znd0Agd+6e9NIiE6TeKGiT3LNNkUc1ThhXZmFOROCX/ueve3PUvIEHYxqGirZDAs
2w76lQZl35Mj/HeRGKdj875EEZQy6AIHenQXJCrhY2WFJMMAumiMoK4jMGl5Zosu
Y8vaLk1AgjEGhKsdwCMS0rkKmaKMgZeaYN86O4WAi+0cPstGQE8aPtA=
=59yx
-----END PGP SIGNATURE-----
@tarotene
Copy link
Author

tarotene commented Feb 9, 2025

How to Verify the Statement

This Gist contains three files:

  1. Key_Transition_Statement_1.md
    • The Key Transition Statement in Markdown format.
  2. Key_Transition_Statement_1.old.asc
    • The detached signature made with my old key.
  3. Key_Transition_Statement_1.new.asc
    • The detached signature made with my new key.

To verify the authenticity of the statement, please download all three files to the same directory and run the following commands in a terminal:

gpg --verify Key_Transition_Statement_1.old.asc Key_Transition_Statement_1.md
gpg --verify Key_Transition_Statement_1.new.asc Key_Transition_Statement_1.md

If the verification is successful, GnuPG will indicate that the file was signed by the corresponding key. This confirms that the statement in Key_Transition_Statement_1.md was indeed signed by both the old and the new keys.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment