| Age | Commit message (Collapse) | Author |
|---|
|
In order to replace leap_auth with bonafide, we created a
class to hold the user credentials
|
|
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 covered a lot of missing cases on the keymanager tests. We also
isolated these tests, that caused some other tests to break, so we
fixed them.
|
|
I added a new test to check that an existing public key is not being
sent to leap on 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
|
|
|
|
Some keymanager api was updated, so we needed to update some calls.
|
|
|
|
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
- 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 #604
|
|
- Issue #591
- using leaps should_redownload for check
|
|
- Issue #591
|
|
- Issue #586
|
|
|
|
- fixing build
Issue #586
|
|
close soldedad and remove it from cache
Issue #586
|
|
|
|
- Issue #587
|
|
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 #485
- Problem was that register starts ZMQ without a session every time
soledad is used
- This reverts commit 36b9261f609901b83da4f8915640eb6043530f01
|
|
--Issue #485
|
|
|
|
- See 660e0d9de
|
|
Imap account creation was firing post sync hooks
and that was trying to use the mailboxes that were
not synced yet. Just moved that for the after sync
together with the incoming mail fetcher
|
|
Setting up the incoming mail fetcher checked for an INBOX
before the first sync, that created an INBOX on every new
machine and when you removed the leap folder.
We moved that right after the initial sync, along the
generation of the OpenPGP keys and adapted the tests
|
|
|
|
need_sync is not part of api anymore and will not be any time sooner.
Removing unnecessary skipped test.
|
|
- Issue #420
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The latest changes on the platform caused the user agent to be
unable to download the smtp client certificate, receiving a 401 in
response. I added the authorization header to the call on the user
agent so that is fixed.
|
|
|
|
|
|
otherwise
|
|
|
|
|
|
|
