bitmask-dev.git/src/leap/bitmask/keymanager, branch master

[feat] extend the expiration of private keys if needed

2017-12-03T22:12:14+00:00

Check on every fetch of the private key if the expiration is less than
two months before it expire. And extend the expiration if needed.

- Resolves: #8217

[refactor] remove rengenerate key

2017-12-03T19:43:38+00:00

We are not planning to regenerate keys (for now), only to extend the
expiration date.

[feat] stop resetting signs used after key regeneration

2017-12-03T19:43:37+00:00

We were considering to reset the sign_used flag to force the new key to
be resend as attachment in forthcoming emails. Although, this is not a
good solution, because we'll lose information about which keys the
client has signed.

[bug] remove change_key_expiration from the API

2017-12-03T19:43:37+00:00

This was intended to offer the option of only extend the old key and
not change it for a new one. However, we don't plan to use this
behavior anymore.

[bug] specify _get_inactive_private_keys as a private method

2017-12-03T19:43:36+00:00

[refactor] rename key extension to expiration

2017-12-03T19:43:35+00:00

This changes reflect python-gnupg naming.
With @aarni

[bug] fix log of the key being fetched

2017-12-03T19:43:35+00:00

[bug] remove key generation event from regenerate_key

2017-12-03T19:43:34+00:00

The KEYMANAGER_FINISHED_KEY_GENERATION event is used to send a welcome
mail to the users, which was causing a new welcome mail when
regenerating a key. We removed the event from regenerate_key method.

We should implement a KEYMANAGER_FINISHED_KEY_REGENERATION event when
it's needed.

[bug] change edit-key to use fingerprint as param

2017-12-03T19:43:34+00:00

python-gnupg doesn't accept address as parameter for --edit-key

[feat] expired public key are remotely fetched if expired

2017-12-03T19:43:33+00:00

- private key is not allowed to be fetched remotely
- fetch_remote needs to be specifically set
- if a new key is fetched (ie different KeyID), the validation
  rule applies