bitmask-dev.git/tests/integration/keymanager, branch 0.10.7 [bitmask-dev] [feat] extend the expiration of private keys if needed 2017-12-03T22:12:14+00:00 Ruben Pollan meskio@sindominio.net 2017-10-31T10:02:00+00:00 fb7eef011cc672f1884bcfcd4c859a549d8f3e49 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 
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 Ruben Pollan meskio@sindominio.net 2017-10-31T09:36:35+00:00 f6c71494f0ada864e80ee74c60ec09939a14f44b We are not planning to regenerate keys (for now), only to extend the expiration date. 
We are not planning to regenerate keys (for now), only to extend the
expiration date.
[test] fix key renew test 2017-12-03T19:43:38+00:00 Ruben Pollan meskio@sindominio.net 2017-10-26T16:35:19+00:00 d13fb37acd01dc1e4d62631e0e131a937a001f33 






[feat] stop resetting signs used after key regeneration
2017-12-03T19:43:37+00:00

Tulio Casagrande
tcasagra@thoughtworks.com

2017-04-21T21:27:36+00:00

6300a435aaf3f4dacd4615c75defaa8ea7369248

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.





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

Tulio Casagrande
tcasagra@thoughtworks.com

2017-04-10T21:52:20+00:00

85c0e9b95dfc3d7134e47aac7e7e485270b42b96

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.





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

Tulio Casagrande
tcasagra@thoughtworks.com

2017-04-10T21:45:17+00:00

873012e432cd6125c3174a2bc6ef9498166d94ea












[refactor] rename key extension to expiration
2017-12-03T19:43:35+00:00

Tulio Casagrande
tcasagra@thoughtworks.com

2017-02-15T17:40:30+00:00

d80b8774914dd21b9d61ecd4b3c3f3fe66e1c182

This changes reflect python-gnupg naming.
With @aarni





This changes reflect python-gnupg naming.
With @aarni







[bug] fix expected new_expiry_date
2017-12-03T19:43:34+00:00

Tulio Casagrande
tcasagra@thoughtworks.com

2016-12-20T18:51:35+00:00

3a9c3ca2663aa4fdcacfe0a3d73061ec1946c54a

Previously, new_expiry_date was calculated by the key creation date + 1
week, but the proper behavior is today + 1 week, accordingly with gpg
behavior.





Previously, new_expiry_date was calculated by the key creation date + 1
week, but the proper behavior is today + 1 week, accordingly with gpg
behavior.







[feat] expired public key are remotely fetched if expired
2017-12-03T19:43:33+00:00

NavaL
ayoyo@thoughtworks.com

2016-11-29T18:28:52+00:00

026de868a3f301abea2671dfd7d858e73f3bb755

- 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





- 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







[bug] sign_used flag is reset for all public keys when the key expiration date is extended
2017-12-03T19:43:32+00:00

NavaL
ayoyo@thoughtworks.com

2016-12-05T14:12:56+00:00

a164b1daa6bcbbf6bffe84d6b02ed2be43c29e7f

- this is required so that the key is re-attached to the first
outgoing email to all users who already have the expired key.





- this is required so that the key is re-attached to the first
outgoing email to all users who already have the expired key.