| 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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit d10f607a4d40587510b0dc31b31fe4750bf4a3a3, reversing
changes made to c28abba2f5b1186c671ebef508d40ffaae6d5bc5.
|
|
|
|
|
|
|
|
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
|
|
SMTP json is a blocking HTTP request that was taking ~1 sec
of the session creation. We moved it to the UA initialization
|
|
Soledad json must only be downloaded after we
fetch the api provider certificate, we can't
make the request for it before having this cert
|
|
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
|
|
Authentication is now consistently done before
creating the leap session, so I removed the
auth attempt from inside the leap session
factory
|
|
It is already done earlier in the bootstrap and
is not user specific, so shouldn't be done on
user bootstrap
|
|
Some keymanager api was updated, so we needed to update some calls.
|
|
|
|
There is an update on leap_mail where an user id became required to
create an Account. So, this change update the Account usage on user
agent to pass this parameter.
|
|
Migrate all usage of leap.ImapAccount to leap.Account
We had to adapt some calls because of signature changes and, because
we need the Account to be initialized before moving on, we are directly
using the deferred initialization that the account has
See: https://github.com/leapcode/leap_mail/pull/228
|
|
- Issue #615
- IMAPAccount ctor reuses same instance for all accounts
|
|
- Issue #615
- invalid token raised by soledad after timeout,
if we see this, recreate the session on next login
|
|
- Issue #615
- Fixed some long broken but not failing tests
|
|
- Issue #591
- using leaps should_redownload for check
|
|
- Issue #591
|
|
- Issue #586
|
|
- Issue #586
|
|
close soldedad and remove it from cache
Issue #586
|
|
|
|
- Issue #587
|
|
Issue #583
|
|
It was rising an error when UA tried donwload the certificate and the
directory that file will be create doesn't exist yet
|
|
- Issue #576
|
|
|
|
|
|
The SoledadSession class was removed and some methods implemented there
was moved to LeapSessionFactory and LeapProvider
|
|
|
|
- Issue #499
- Some smaller refactorings
- Extract smtp cert download to own class
|
|
We removed the common parts from the bitmask libraries smtp
and adapted the tests.
We also advanced the new mail sender implementation, but it
is coupled to the twisted.mail.smtp.User currently and we need
to adapt leap mail to remove this dependency
|
|
- Issue #499
- No longer needs local smtp port
|
|
|
|
- Issue #485
- Problem was that register starts ZMQ without a session every time
soledad is used
- This reverts commit 36b9261f609901b83da4f8915640eb6043530f01
|
