Skip to content

[WIP] Feat regenerate key

ayoyo requested to merge (removed):feat_regenerate_key into master
  • This is the first step of the key regeneration...
  • It depends on a specific branch of python-gnupg https://github.com/pixelated/python-gnupg/tree/key_extension_and_sign which is merge of https://github.com/isislovecruft/python-gnupg/pull/168 and https://github.com/isislovecruft/python-gnupg/pull/167
  • The implementation includes:
    • A one day extension of the current if already expired, before generating the new key-pair.
    • The new key pair is signed by the old key, then the old private key is deactivated, and old public key removed (this is not required for the next step).
    • Also, the sign_used flag is reset to indicate that the user has not yet received an encrypted email from any of the contacts using the new public key.
  • This is done under the assumption of only one key pair allowed per keymanager storage. The next step, that is allowing more than one key pair in key manager, will be in a separate PR that will be done on top of this.
  • Hence, this PR doesn't need to be merged... but is done so that people can see what is happening... and hopefully get feedback.

Merge request reports