Advertisement
Guest User

Untitled

a guest
Oct 24th, 2014
157
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.68 KB | None | 0 0
  1. Hello,
  2.  
  3. Fri Oct 24 12:08:28 EDT 2014
  4.  
  5. For a number of reasons, I've recently set up a new OpenPGP key,
  6. and will be transitioning away from my old one.
  7.  
  8. The old key will continue to be valid for some time, but I prefer all
  9. future correspondence to come to the new one. I would also like this
  10. new key to be re-integrated into the web of trust. This message is
  11. signed by both keys to certify the transition.
  12.  
  13. The old key was:
  14.  
  15. pub 4096R/2E177CFD 2013-10-23 [revoked: 2014-10-23]
  16. Key fingerprint = A96A 9E4D BE08 B18B 55F6 751A 0579 F578 2E17 7CFD
  17.  
  18. And the new key is:
  19.  
  20. pub 4096R/4372F24A 2014-10-23 [expires: 2017-10-22]
  21. Key fingerprint = C765 FAD7 824B C74A 515F 938B EC24 32D1 4372 F24A
  22. `
  23. To fetch the full key from a public key server, you can simply do:
  24.  
  25. gpg --keyserver pgp.mit.edu --recv-key 4372F24A
  26.  
  27. If you already know my old key, you can now verify that the new key is
  28. signed by the old one:
  29.  
  30. pub 4096R/4372F24A 2014-10-23 [expires: 2017-10-22]
  31. uid [ultimate] Neal Trischitta <ntrischi@stevens.edu>
  32. sig!3 4372F24A 2014-10-23 Neal Trischitta <ntrischi@stevens.edu>
  33.  
  34. sub 4096R/BDA40E6E 2014-10-23 [expires: 2017-10-22]
  35. sig! 4372F24A 2014-10-23 Neal Trischitta <ntrischi@stevens.edu>
  36.  
  37. If you don't already know my old key, or you just want to be double
  38. extra paranoid, you can check the fingerprint against the one above:
  39.  
  40. pub 4096R/4372F24A 2014-10-23 [expires: 2017-10-22]
  41. Key fingerprint = C765 FAD7 824B C74A 515F 938B EC24 32D1 4372 F24A
  42. uid [ultimate] Neal Trischitta <ntrischi@stevens.edu>
  43. sub 4096R/BDA40E6E 2014-10-23 [expires: 2017-10-22]
  44.  
  45. If you are satisfied that you've got the right key, and the UIDs match
  46. what you expect, I'd appreciate it if you would sign my key. You can
  47. do that by issuing the following command:
  48.  
  49. **
  50. NOTE: If you have previously signed my key but did a local-only
  51. signature (lsign), you will not want to issue the following, instead
  52. you will want to use --lsign-key, and not send the signatures to the
  53. keyserver.
  54. **
  55.  
  56. gpg --sign-key 4372F24A
  57.  
  58. I'd like to receive your signatures on my key. You can either send me
  59. an e-mail with the new signatures (if you have a functional MTA on
  60. your system):
  61.  
  62. gpg --export 4372F24A | gpg --encrypt -r 4372F24 --armor | mail -s 'OpenPGP
  63. Signatures' ntrischi@stevens.edu
  64.  
  65. I also highly recommend checking out the excellent Riseup GPG best
  66. practices doc, from which I stole most of the text for this transition
  67. message ;-)
  68.  
  69. https://we.riseup.net/debian/openpgp-best-practices
  70.  
  71. Please let me know if you have any questions, or problems, and sorry
  72. for the inconvenience.
  73.  
  74. --
  75. v/r,
  76. Neal Trischitta
  77. Stevens Institute of Technology
  78. Class of 2015
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement