bitmask-dev.git/tests/integration/keymanager, branch travis [bitmask-dev] [feat] add fetch key by fingerprint to keymanager 2017-10-26T16:37:05+00:00 Ruben Pollan meskio@sindominio.net 2017-10-24T09:53:10+00:00 5243c7eb4c58a4419da2103af8c1e4004f01053b - Resolves: #9023 
- Resolves: #9023
[bug] make nicknym return key data 2017-10-26T16:37:04+00:00 Ruben Pollan meskio@sindominio.net 2017-10-24T09:50:30+00:00 d16b25da0962156601615587a612b57b918b0dc6 There was a mismatch on the return values of Nicknym class and the expectations. As most of the code was expecting an OpenPGPKey, but it was returning the json as it came from the nickserver. Now is just returning the key data. 
There was a mismatch on the return values of Nicknym class and the
expectations. As most of the code was expecting an OpenPGPKey, but it
was returning the json as it came from the nickserver. Now is just
returning the key data.
[test] ca_cert_path can not be an empty string 2017-07-18T20:38:17+00:00 Ruben Pollan meskio@sindominio.net 2017-07-18T20:38:17+00:00 2b239d73868b69db083de517b26498b7888b3650 






[feat] push private key updates into nicknym
2017-06-12T18:34:15+00:00

Ruben Pollan
meskio@sindominio.net

2017-06-08T09:14:38+00:00

f0117969b19e05d568a108b12390c47a011576f6

Deal as well with sending key if key is outdated in the providers nicknym.

- Resolves: #8819, #8832





Deal as well with sending key if key is outdated in the providers nicknym.

- Resolves: #8819, #8832







[tests] fix tests
2017-04-27T17:33:30+00:00

Kali Kaneko (leap communications)
kali@leap.se

2017-04-26T16:56:49+00:00

13760d78fba87570c91c0a2e702980d2ec45a0ed

mock a renamed method.





mock a renamed method.







[test] remove randomness tester
2017-04-03T13:45:53+00:00

Ruben Pollan
meskio@sindominio.net

2017-04-03T09:27:21+00:00

9883c75446187af0f88e03af75b42e8d3773fa18

There was a test in the Keymanager refresher that was testing the
randomness of the refreshing intervals. It was producing a bunch of
intervals and checking that all of them where different. This test
(rarelly) fails some times, but this is not a sign of bad randomness.

- Resolves: #8813





There was a test in the Keymanager refresher that was testing the
randomness of the refreshing intervals. It was producing a bunch of
intervals and checking that all of them where different. This test
(rarelly) fails some times, but this is not a sign of bad randomness.

- Resolves: #8813







Check validity of key signature
2017-01-26T13:55:11+00:00

Zara Gebru
zgebru@thoughtworks.com

2016-06-16T12:41:54+00:00

847bc7ddd051c4656d86a6eda1b4e6cbdb5b1c5e

Check if a new fetched key was signed by a old key with the same address.

Please do not merge before: https://github.com/isislovecruft/python-gnupg/pull/150

- Resolves #8112





Check if a new fetched key was signed by a old key with the same address.

Please do not merge before: https://github.com/isislovecruft/python-gnupg/pull/150

- Resolves #8112







[tests] fix keymanager tests after refactor and merge
2016-11-22T14:57:05+00:00

Zara Gebru
zgebru@thoughtworks.com

2016-11-18T15:51:27+00:00

1baa817b567cc234e76faafc5ec92cfa75222ba6

- some pep8 problems
- some confusion with old and new code after merging
from old keymanager





- some pep8 problems
- some confusion with old and new code after merging
from old keymanager







[tests] fix some refresher tests after the refactor
2016-11-22T14:57:04+00:00

Kali Kaneko (leap communications)
kali@leap.se

2016-11-04T14:42:12+00:00

0871c96aa71d9b9112a90ab7cc6d4adfc3cd7fa4

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?





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?







[feature] keymanager: background update keys
2016-11-22T14:57:03+00:00

Zara Gebru
zgebru@thoughtworks.com

2016-07-08T09:55:55+00:00

e5717e853af7d2f91ac69e66c1b2ee058289e78d

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





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