summaryrefslogtreecommitdiff
path: root/src/leap/bitmask/keymanager/__init__.py
AgeCommit message (Collapse)Author
2017-10-26[feat] add fetch key by fingerprint to keymanagerRuben Pollan
- Resolves: #9023
2017-10-26[bug] make nicknym return key dataRuben Pollan
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.
2017-07-14[bug] handle 503 responses from nyckserverRuben Pollan
This can be produced by errors fetching keys from the server. - Resolves: #8971
2017-06-28[docs] fix the docstring since the implementation does not sign yetKali Kaneko (leap communications)
2017-06-13[bug] fix keymanager issues with last mergeRuben Pollan
2017-06-12[feat] push private key updates into nicknymRuben Pollan
Deal as well with sending key if key is outdated in the providers nicknym. - Resolves: #8819, #8832
2017-04-27[bug] unify logging style using class attrKali Kaneko (leap communications)
I changed most of the logger statements to use a class attribute, in this way it's easier to identify which class it's logging them. in some cases I leave a module-level logger, when we're either using functions or when the module it's too small. at the same time I did a general review and cleanup of the logging statements.
2017-01-19rename some varsZara Gebru
2016-11-30[bug] make srp token changes propagate to nicknym objectKali Kaneko (leap communications)
the token is set when we get the srp token in the keymanager service, but it wasn't been propagated properly to the internal nicknym object that was refactored recently. here I make the setter write the same token to both keymanager itself and the nicknym. some little additional refactors: - move gpg initialization to a helper method in this way it becomes easier to stub the soledad and keymanager components, for testing. - name nicknym token as publicly visible, since i'm accessing it from the keymanager object. - Resolves: #8651
2016-11-22[tests] fix keymanager tests after refactor and mergeZara Gebru
- some pep8 problems - some confusion with old and new code after merging from old keymanager
2016-11-22[refactor] use qualified exceptionsKali Kaneko (leap communications)
2016-11-22[feature] keymanager: background update keysZara 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-11-03[style] pep8 fixesKali Kaneko (leap communications)
2016-10-21[bug] fail gracefully if cannot find cert fileKali Kaneko (leap communications)
2016-10-07[style] pep8Kali Kaneko (leap communications)
2016-10-07[refactor] use new logger infrastructureKali Kaneko (leap communications)
2016-09-29[bug] remove destructor, pass combined_ca_bundle as optional paramKali Kaneko (leap communications)
this brings back a couple of commits by pixelated that were missed in my keymanager merge. https://github.com/leapcode/keymanager/commit/354ad5a12e90463f9952fe056f191c6d4cdadf40 https://github.com/leapcode/keymanager/commit/dd7ba606df2909c76b20b1d4bb0134302f94b3d0 basically it removes the destructor (there's no guarantee that it gets executed!) and it addds the combined ca bundle as an optional parameter to keymanager initialization
2016-09-22[bug] only generate key if soledad has ever synceddrebs
2016-09-01[refactor] remove unneeded version infoKali Kaneko (leap communications)
2016-08-29[pkg] mv keymanager to leap.bitmask.keymanager submoduleKali Kaneko (leap communications)