You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2019. It is now read-only.
It is a good idea to regenerate public keys every once in a while. Previously, the cumbersome nature of PGP web of trust certification has kept people from doing this as frequently as possible. With a certifying keyserver, this should no longer be an issue. Therefore, it would make sense to (eventually) have a specialized facility for performing a transition from one key to another. This would involve.
Adding a a new PGP public key to the keyserver profile
Setting the previous one to expire soon.
Waiting for outstanding email (signed under the old key) to be delivered.
Removing the old public key from the profile
Possibly waiting some more until it is believed that all mail encrypted to the old key has been received.
Securely erasing the old key.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It is a good idea to regenerate public keys every once in a while. Previously, the cumbersome nature of PGP web of trust certification has kept people from doing this as frequently as possible. With a certifying keyserver, this should no longer be an issue. Therefore, it would make sense to (eventually) have a specialized facility for performing a transition from one key to another. This would involve.
The text was updated successfully, but these errors were encountered: