summaryrefslogtreecommitdiff
path: root/service/pixelated/bitmask_libraries/keymanager.py
AgeCommit message (Collapse)Author
2017-01-10Change the logger.info to logger.debugTayane Fernandes
Given that we don't need to expose the user fingerprint every time we login, we changed to log it only on debug mode. See #815
2017-01-10Check if key is synchronized with server at every loginTulio Casagrande
This is a temporary solution when uploading a regenerated key fails. It's going to attempt the upload again on the subsequent logins. The drawback with this solution, is that the fetch remote can increase the login time, specially with multiple users. See: #815
2017-01-09Log user's current key for easier debugTulio Casagrande
Related with: #815
2017-01-06Raise exception when sending a renerated key failsTulio Casagrande
We still need to figure out what to do when the upload fails. But we're already raising the exception, so we can track it on the logs See: https://github.com/pixelated/pixelated-user-agent/issues/815
2017-01-02Removes unused methodThais Siqueira
2017-01-02[#851] minor refactoring, and using the right keymanager branchNavaL
2017-01-02[#850] refactoring as a result of moving should_renew to be in keyNavaL
2017-01-02[#850] keys will now be renewed two months before expiry dateNavaL
2017-01-02[#815] regenerating new keys when the current one expiresNavaL
2017-01-02[#815] regenerating new keys when the current one expiresNavaL
2016-10-19Adapted logging in the UA to use twisted.loggerBruno Wagner
2016-10-18Adapted imports to reflect new bitmask-dev dependencyBruno Wagner
2016-09-13[#778] Handling case of failed key uploadTulio Casagrande
If we get any problem with the upload of the user's public key, we are deleting the key pair from the local database and denying login. That way, a new login will have a chance to regenerate the key and upload it properly.
2016-09-13[#778] Renaming get_key to be consistent with keymanagerTulio Casagrande
2016-09-08Only send public key if a new key was generatedBruno Wagner
We were always sending the public key to nicknym, even if it was already there. The send_key method purpose is to update the public key in case a new pair is created and shouldn't be done at every login
2016-08-30[#765] Move combined certificates to the leap folderTulio Casagrande
Since we are creating the combined certificates at the beginning of the UA and using it for multiple users, it makes more sense to create it in the leap folder instead of on a temporary file This bundle will be updated on every UA start
2016-08-29[#765] Move combined_ca_bundle to UA initializationTulio Casagrande
With this change we don't have to create the combined_ca_bundle for every user at every login. To support this change, we started migrating away from the LeapCertificate class that was making the LeapProvider setup more brittle
2016-08-19Started deferring leap session creation #759Bruno Wagner
Started adapting get_leap_session to deferreds Soledad and keymanager setup calls will now happen in deferreds and leap session creation itself is a deferred with callbacks This is a start in breaking the big blocking calls we were doing on the main thread, this was done without changing code inside the leap libraries yet so things can be further optimized This breaks the ~4 seconds get_leap_session piece into smaller 1 seconds one, that can be further optimized and deferred to even smaller calls There are requests calls happening on the main thread that should get this number even further down Also moved some pieces from bitmask libraries to our bootstrap, because they are not bitmask libraries anymore and that was causing confusion