| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
- Resolves: #8069
- Releases: 0.9.2
|
|
https://github.com/meskio/bitmask_client into develop
|
|
|
|
|
|
|
|
this box is only visible when the HAS_PIXELATED flag is True, that
means we have pixelated-user-agent and pixelated-www in the environment.
- Releases: 0.9.2
|
|
|
|
|
|
always quit
- log the init_platform failure to the critical log
- return True/False in initializer
- remove implementation to install driver and display informative message instead
|
|
- Resolves: #8041
- Releases: 0.9.2
|
|
|
|
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
|
