| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This greatly simplifies the handling of the password in the thunderbird
extension.
- Related: #6041
|
|
|
|
|
|
|
|
|
|
This includes getting the token for the imap authentication, and
displaying it on the help window.
- Resolves: #4469
- Releases: 0.10.0
|
|
Adapt to users emitting the userid/uuid too.
- Resolves: #7656
- Releases: 0.10.0
|
|
|
|
- Resolves: #7585
|
|
https://www.transifex.com/otf/bitmask/translate/#ar/$/31977726
https://www.transifex.com/otf/bitmask/translate/#nl/$/32117870
https://www.transifex.com/otf/bitmask/translate/#ar/$/22113277
https://www.transifex.com/otf/bitmask/translate/#nl/$/22113279
|
|
|
|
- Related: #7552
|
|
Add a UI message for the user to know where to go next.
This message goes away after 60 seconds or right after a MUA logs in.
- Resolves: #7552
|
|
|
|
|
|
Connecting to the `soledad_bootstrap_finished` signal is not enough
since the password change window is created after the signal is emitted,
that way we were not able to tell when soledad is ready to be used.
- Resolves: #7474
|
|
these methods were returning None, and therefore breaking soledad
password change (since it checks whether mail is enabled before changing
soledad pass after srp pass change).
- Resolves: #7470
|
|
Right after a complete sync we show the unread emails.
- Resolves: #7453
|
|
|
|
- Resolves: #7415
|
|
Look for file defined in the `BITMASK_CREDENTIALS` env variable and load
`provider`, `username` and `password` data.
Trigger login if they were loaded correctly.
The credentials file should look like this:
[Credentials]
username = my-account@my-provider.com
password = secret
- Resolves: #7419
|
|
|
|
|
|
If the user wants to register a new account we check whether the
provider allows registration or not right after getting the
provider.json file and show an error msg on the wizard if not allowed.
Also, there is a new signal to handle the error raised by the server if
a registration attempt is made but is rejected with error 403.
- Resolves: #6594
|
|
Register to Soledad's sync (send and receive) events and display the
progress in the UI.
- Resolves: #7353
|
|
Also, do not raise assertionerror, log warning instead.
|
|
- Resolves: #7284
|
|
Prevent locks caused by the zmq log handler reaching the zmq's HWM (High
water mark / buffer limit) and causing some components to block until
the buffer is empty (running the zmq handler for instance).
We run the zmq handler in the background all the time to prevent this.
- Resolves: #7222
|
|
Replace logging.getLogger with custom get_logger.
Remove some unneeded dependencies and reorder other.
|
|
- Add a new handler for a zmq/thread-safe log send between components.
- Update the log window to use this new handler.
- Remove old custom handler
We have implemented a new handler that uses logbook, so this one is no
longer needed.
- Adapt log silencer to new handler
- Use log file always as default
- Related: #6733
|
|
- Related: #6359
|
|
Before this commit, the backend used plain pyzmq bindings for communicating
with the frontend. This implements the txzmq twisted-powered bindings instead.
Closes: #6360
|
|
If the quit() call is triggered by the system logout we should not
disable the autostart. Otherwise bitmask won't autostart on the next
session start.
- Resolves: #6424
|
|
Catch the keyring.errors.InitError exception.
The automatic login sequence now stops correctly instead of freezing if
the user cancel the keyring open operation.
- Resolves: #6682
|
|
After a provider fails to pass the checks, the providers combo box is
not enabled when it should, we just took care of the provider line edit.
- Resolves: #6418
|
|
Also set text to 'bold' so it's easier to find at a first sight.
- Resolves: #5526
|
|
FIX: Login attempt is made against previously selected provider.
Closes #6654.
Cherry-picked from release/0.8.x since it's a very annoying bug for the
testing cycles for the next release (0.9.0) -- kali.
|
|
|
|
|
|
|
|
FIX: Login attempt is made against previously selected provider.
Closes #6654.
Remove unused comments as well.
|
|
This causes (on certain scenarios) the app to segfault and it is really
hard to debug.
|
|
Now it's working and no longer segfaults, so we can enable safely this
feature again.
Stop tracking the gui connections on wizard.
|
|
|
|
This temporary hack prevents the app to have segfaults when the first
run wizard finishes.
For more information look at https://leap.se/code/issues/6597
|
|
Fix typo for signal disconnection.
The backend is the one who always creates the certificates. Either if it
is run separately or in a process in the same app as the frontend.
|
|
Add the 'check_online' method to check whether the backend is accessible
or not.
Reduce the wait for running threads timeout on quit.
Add retry feature to the backend requests send.
|
|
- factor out the signal tracking code as a helper class,
- move login logic from MainWindow to LoginWidget,
- add new signals to the LoginWidget to interact with MainWindow,
- add login sequence docs to LoginWidget class,
- improve docs for login methods,
- add LoginState class to handle login states,
- disable login button until data is entered,
- move some properties and actions to .ui file.
|
|
Closes #6150.
|
