bitmask-dev.git - [bitmask-dev]

Age	Commit message (Collapse)	Author
2017-12-03	[bug] remove change_key_expiration from the API	Tulio Casagrande
	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.
2017-12-03	[bug] specify _get_inactive_private_keys as a private method	Tulio Casagrande

2017-12-03	[refactor] rename key extension to expiration	Tulio Casagrande
	This changes reflect python-gnupg naming. With @aarni
2017-12-03	[bug] fix expected new_expiry_date	Tulio Casagrande
	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.
2017-12-03	[feat] expired public key are remotely fetched if expired	NavaL
	- 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
2017-12-03	[bug] sign_used flag is reset for all public keys when the key expiration ↵	NavaL
	date is extended - this is required so that the key is re-attached to the first outgoing email to all users who already have the expired key.
2017-12-03	[feat] expired public key are remotely fetched if expired	NavaL
	- 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
2017-12-03	[bug] decryption will be tried for all inactive keys	NavaL

2017-12-03	[feat] decryption interoperability, when the current key pair	NavaL
	is renewed - there is only one private inactive key that is the key expiring last among all inactive keys - if there is an inactive key, decryption with it, is tried if it fails with the current active key.
2017-12-03	[feat] reset sign_used flag after regenerating key pair	NavaL
	- this flag is used by leap.mail to attach the new key
2017-12-03	[feat] first phase of key regeneration	NavaL
	- if current key pair is expired, it'll be extended for a day first - new key pair will be signed by the old key
2017-12-03	[feat] add key expiry date extension in keymanager	NavaL
	- extends key pair (unlocked from soledad) - extension period is counted from key creation date
2017-10-26	[feat] add fetch key by fingerprint to keymanager	Ruben Pollan
	- Resolves: #9023
2017-07-18	[test] ca_cert_path can not be an empty string	Ruben Pollan

2017-06-12	[feat] push private key updates into nicknym	Ruben Pollan
	Deal as well with sending key if key is outdated in the providers nicknym. - Resolves: #8819, #8832
2017-04-27	[tests] fix tests	Kali Kaneko (leap communications)
	mock a renamed method.
2016-11-22	[tests] fix keymanager tests after refactor and merge	Zara Gebru
	- some pep8 problems - some confusion with old and new code after merging from old keymanager
2016-11-22	[tests] fix some refresher tests after the refactor	Kali Kaneko (leap communications)
	disabled some tests that were failing, for some reason the twisted logger doesn't want to be patched? besides, I don't think it's a good idea to rely on log information for tests. what is it really that we were trying to test there?
2016-11-22	[feature] keymanager: background update keys	Zara Gebru
	Port of the original commit: 8f1fe8dd4a54fd2bdda2fc78c339ce9b3d0fc331 by Zara Gebru that introduced updating keys in the background. This was made in the legacy leapcode/keymanager repo, but was lost in the merge to the unified bitmask-dev. Original commit message follows: -------------------------------- - refresh random key in random time - add get key by fingerprint - refactor nicknym methods to own file - tests - note this do not include a check for revoked key, since that need some changes in gnupg - Related: #6089
2016-10-07	[tests] remove assertion, bundles are not deleted on exit	Kali Kaneko (leap communications)

2016-09-06	[tests] factor out the common pieces to keymanager.testing	Kali Kaneko (leap communications)

2016-09-01	[tests] move tests to root folder	Kali Kaneko (leap communications)