Age | Commit message (Collapse) | Author |
|
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
|
|
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
|
|
Related with: #815
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
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
|
|
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
|
|
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
|
|
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
|