| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
It was rising an error when UA tried donwload the certificate and the
directory that file will be create doesn't exist yet
|
|
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
|
|
- See 660e0d9de
|
|
|
|
longer starts the smtp server
|
|
otherwise
|
|
|
|
|
|
|
|
|
|
external srp leap library
|
|
-- Issues #93 and #333
|
|
- Issue #333
- Needed to patch urrlib3 for older requests versions
- Use --leap-cert-fingerprint <SHA1> to validate fingerprint
|
|
- Issue #333
- Now a different certificate is used to communicate with the provider's
HTTPS website than for all other connections, e.g. to the api
|
|
|
|
|
|
|
