| Age | Commit message (Collapse) | Author |
|---|
|
|
|
We don't update the polkit file normally, for now let's check if it's
installed. It should be more clever, detecting wich file is needed,
depending on wich bitmask-root will be executed. But for now it's just a
dummy check.
|
|
polkit doesn't work inside docker.
|
|
|
|
Since bonafide was not catching the error 401, an attempt to bootstrap a
provider that does not support anonvpn with the new setup was resulting
in a json that was containing only an error message.
this was producing an error when trying to access the configuration for
that provider's EIP section.
we now avoid writing a json config file if an error 401 is found, and
also catch the exception for a ValueError when the EIP section is not
found in the provider's configuration.
|
|
|
|
|
|
for some usages, specially with autostart enabled, user might want to
launch only the systray.
this commit implements a simple ``--nowindow`` switch that just avoids
showing the main window for now. in the future, we can have a different
entrypoint that just launches bitmaskd and a minimal systray widget.
I'm not documenting this feature properly since I think this is still
missing some functionality: the ability to switch on and off the vpn,
and the ability to pass the --autostart as a flag to the bitmask
entrypoint.
|
|
also refactor and move polkit_agent so that it does not depend on having
bitmask on the path.
|
|
|
|
|
|
|
|
|
|
for now, we'll be hardcoding tcp as a more reliable alternative, no
matter what the provider announces.
explicitely specifying ipv4 should fix the case in which vpn fails to
start because ipv6 is disabled.
-Resolves: #9181, #9129
|
|
honor the anonymous certificate for the providers that offer it.
this still needs a change in bonafide, in which if provider supports
anonymous access we still have to download eip-service.json
for testing, I assume this has been already manually downloaded.
|
|
|
|
|
|
- Resolves: #9202
|
|
|
|
|
|
|
|
In ubuntu 17.10 some changes with systemd-resolved broke our firewall,
blocking all DNS queries. The masquerade rules in the firewall, that
are used to rewrite the source IP address of the DNS queries, were
wrongly modifying the queries to systemd-resolved.
Let's apply masquerade only to the packets addressed to the nameserver.
- Resolves: #9137
|
|
|
|
Removing '--persist-ip' param on openvpn it will try to connect to a
different gateway if the first one fails. This means, that in case of
network disconnection for some minutes bitmask will keep rotating
between the different gateways and one the network comes back it will
not connect anymore to the first one, but to the one that was trying at
this moment.
- Resolves: #9188
|
|
|
|
this commit deprecates qtwebkit usage.
|
|
used from both entrypoints for linux and mac apps.
|
|
some juggling to make systray (qt5 for now) and browser (pywebview,
native) start and stop coordinatedly.
I will explore a more lightweight systray for coming releases.
|
|
|
|
If you try to fetch the incoming service while it's still starting it
throws a KeyError.
- Resolves: #9174
|
|
I should remember this change when we merge elijah's fix again.
Hopefully that happens soon enough.
|
|
It has been reported that, after this fix, dns leaks happen under some
circumstances not yet clear. Preparing for a release, we have decided to
revert this change until the problem can be properly triaged.
This means a broken vpn aartful support for the time being, but a
non-leaking master.
https://0xacab.org/leap/bitmask-dev/issues/9137
- Related: #9137
|
|
|
|
|
|
|
|
Thunderbird produces message ids with '-' in them.
|
|
To get the status of a single message providing it's mailbox and
message-id. For now it only returns encryption/signature status.
- Resolves: #6914
|
|
To have consistency with all API calls related to messages and start all
of them with msg_*
|
|
This deferred was not used anywhere, but it was called twice.
Provider is a singleton so multiple logins into the same provider where
producing it to be called mor than once.
- Resolves: #9171
|
|
|
|
|
|
|
|
|
|
|
|
Chech the hash of the installed bitmask root and sign as not installed
if doesn't match the one we have in the bundle. Also for running
bitmask-root, if there is more than one (in /usr/local/sbin and
/usr/sbin) run the one with higher version number.
- Resolves: #9020
|
|
Pin the provider.json and the ca cert for the public providers.
- Resolves: #9074
|
|
|
|
Check on every fetch of the private key if the expiration is less than
two months before it expire. And extend the expiration if needed.
- Resolves: #8217
|
|
We are not planning to regenerate keys (for now), only to extend the
expiration date.
|
|
We were considering to reset the sign_used flag to force the new key to
be resend as attachment in forthcoming emails. Although, this is not a
good solution, because we'll lose information about which keys the
client has signed.
|
