Advertisement
Sammey19

Sammey's PGP Message

Apr 8th, 2014
291
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.25 KB | None | 0 0
  1. -----BEGIN PGP SIGNED MESSAGE-----
  2. Hash: SHA512
  3.  
  4. Keybase.io Profile: https://keybase.io/sammey
  5.  
  6. I am Sammey from freenode IRC.
  7. * I am registered in the #bitcoin-otc channel, here, http://bitcoin-otc.com/viewratingdetail.php?nick=Sammey.
  8.  
  9. I am @SamuelFalk19 on Twitter.com (Can be verified on keybase.io the hard-way, if you know how, or go to, http://bit.ly/SammeyTwitterKeybaseProof)
  10.  
  11. I am Sammey1995 on GitHub.com. (Can be verified here, https://gist.github.com/10147336, or on keybase.io)
  12.  
  13. Descendant(s) and/or descendant key(s) from now forward, will be defined as any future PGP Key(s) created as shown in the example below, "Example Creation of Descendant Keys".
  14.  
  15. If the below PGP Key Data is ever revoked, I will sign a message containing my new public PGP Key Information, before time of revocation. This applies dynamically, to every descendant.
  16.  
  17. ==== Begin Example Creation of Descendant Keys ====
  18.  
  19. Key #1 = This Key
  20. Key #2 = Next Key
  21. Key #3 = Key After Key #2
  22.  
  23. Step 1 = Assuming "Key #1" already exists, "Key #2" is created on April 9th, 2014.
  24. Step 2 = "Key #1" Signs a message containing *AT LEAST* the full public key of "Key #2" in the message on April 10th, 2014.
  25. Step 3 = "Key #1" Is revoked and synchronized with keyservers on April 11th, 2014.
  26. Step 4 = "Key #3" Is created on September 16th, 2014.
  27. Step 5 = "Key #2" Signs a message containing *AT LEAST* the full public key of "Key #3" in the message on September 17th, 2014.
  28. Step 6 = "Key #2" Is revoked and synchronized with keyservers on September 18th, 2014.
  29. Step 7 = Steps 4 - 6, can be repeated infinitely, while key numbers in the steps change accordingly in chronological order.
  30.  
  31. ==== End Example Creation of Descendant Keys ====
  32.  
  33. I will refuse to sign a message with any type of authentication algorithm, other than PGP, for a variety of reasons. I will never refuse to sign a message with the PGP Key at the bottom of this message, or the unrevoked descendant of this key. If "I" refuse to to sign with this key, or the unrevoked descendant of this key, "I" am probably an impostor.
  34.  
  35. ==== Begin PGP Key Data ====
  36.  
  37. PGP Key Creation Date: Tuesday, April 8th, 2014
  38. PGP Key Encryption Algorithm Type: RSA
  39. PGP Key Encryption Algorithm Strength: 4096
  40. PGP Key Fingerprint: 7205 E005 B460 30E5 0E66 DD1B 6A61 D05E D8A2 1404
  41. Short PGP Key ID: D8A21404
  42. Long PGP Key ID: 6A61D05ED8A21404
  43.  
  44. ==== End PGP Key Data ====
  45. -----BEGIN PGP SIGNATURE-----
  46. Version: GnuPG v2.0.22 (GNU/Linux)
  47. Comment: Signed on Tuesday, April 8th, 2014 by Sammey
  48.  
  49. iQIcBAEBCgAGBQJTRCMdAAoJEHUDhQ8cuQQN22AP/35Fki5Bg8WBl1l9IvT0dkX+
  50. MhVl/ZxLVcdvFrPfXxUjVf7xfOzTQY7qgbc4RrQ6tDBOjhlVmIRi43rx6QwaCLAB
  51. MVdCBYpp2GhWXvA8sP4JM7rO+oBkkHW/MkckL3K90yNShf+9oXe6+W+cPpW9ZwuU
  52. hz6SpOLiZLJbakCG1XggESaeOp4aYLZdXpeKJx63qlXt5Ts+oz7ozCD3IJsJJZN2
  53. 0oABWRBuiSrCLXmMkc+vo48cA78kIfCFRSbGiACsOChAjS2RRt1sdfzItRaCpurp
  54. L+UlEeReYgLH7mYrVJRAZQXcxDXX+ocMXLYtHUlwDEQfOF0bEXW6+vgUY8qV/6gb
  55. W+6cgS4le3oxwaGhWF3eQ01XsWhKnWfQnfZYPnSzmg7PX+Lt2UxdHcYjp9cDpf11
  56. cIvoMBlL51pIdr7EB2jMTsio9bRGcvia0c8YqJUJrBIYu0cjPRNdvAYDOSsPZTMg
  57. zvOdnIG9nWH2RA4qqNr3/qljkGo4ELsd0lFUvNq2Oemcfikqy1jGwBPBY68q118u
  58. qoTv7S8fDbiDrfFrHieSAowM1RzcclMfnYNEIj/Khg4kdQSALWWxng78Z9BNhRiP
  59. uJ6JwczDVKkYnPVHafX8DZNxTduijT4U4GsYd8R3nbJCtngCXjcKi6guIGsuDZyV
  60. /dxGzdbQucVefpT+yTQb
  61. =C3hl
  62. -----END PGP SIGNATURE-----
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement