| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
we set status to 'off' by default.
- Resolves: #9013
|
|
- Resolves: #9025
|
|
- Resolves: #9003
|
|
|
|
- Resolves: #8973
|
|
We need to update the UI to use the new API.
- Resolves: #8974
|
|
For now we say it will be mixed on every request if the mixnet is
enabled. We might want a better mock in the future.
- Resolves: #8972
|
|
We were encoding some parts as base64 and others with our manual
encoders. Let's not do base64 and use the email standard library
encoders instead.
- Resolves: #8957
|
|
|
|
|
|
|
|
the restarting flag was not being set.
- Resolves: #8959
|
|
|
|
- Resolves: #8992
|
|
Since in OSX the user sees Bitmask in the Dock, I assume that re-launching
Bitmask.app from the /Applications folder means that we can kill the previous
process.
It probably should be able to terminate it gracefully, but we're hitting this
during early testing because of the move to native webview - because the
window.close() method is still not properly hooked.
- Resolves: #9001
|
|
|
|
|
|
|
|
|
|
For now, the way to select a gateway is to add a section in
bitmaskd.cfg:
[vpn_prefs]
locations = ["frankfurt", "seattle__wa"]
countries = ["DE", "US"]
Note that the location indication has priority over country code.
This will be exposed by the UI in release 0.11
- Resolves: #8855
|
|
Old versions of the webapp let agent download an invalid.json, instead
of returning a 404. We try to parse the json, and if no valid json is
found, we use the workaround for manually downloading the service files.
- Resolves: #9004
|
|
|
|
This is a first approach to automatic gateways selection.
More things are missing:
- allow manual selection, by location or country code.
- take the hemisphere into account.
- expose the selected gw to the api/cli
but overall seems this is a good approach to make 0.10 release usable in
terms of vpn.
- Resolves: #8804
|
|
If chromium is installed in the system, there's no need to depend on
qt5.
|
|
this allows for better modularization in, for instance, the debian
package. we should be able to install just the submodules for the vpn
service, or the mail service.
a better modularization needs the mail_services under core to be moved
to bitmask.mail, and do the switch in the main service module for
bitmask daemon.
|
|
- Resolves: #8986
|
|
|
|
In case of the helpers not installed it was crashing the VPNService.
|
|
Just in chance the firewall was not properly cleaned up in a previeous
run (bitmask crashed, some bugs in the code, ...). Let's clean up the
firewall when it starts.
- Resolves: #8979
|
|
|
|
We make an ugly step for that moving the VPNStatus into VPNManagement.
Let's iterate on it a second time to clean up that.
- Related: #8942
|
|
So it's coherent with FirewallManager.
- Related: #8942
|
|
VPNService has knowledge of the tunnel and the firewall and controls
them separately. Also exceptions from VPNControl are handled locally
instead of being propagated.
- Resolves: #8976
- Related: #8942
|
|
if there is no ca_cert passed and the provider is configured, use the
pinned ca cert when the autoconf parameter is true.
|
|
This can be produced by errors fetching keys from the server.
- Resolves: #8971
|
|
Let's also catch the exceptions raised by stopping services so bitmaskd can
stop.
|
|
leap.common is going to handle this
|
|
Let's signal clearly that we don't want to restart it.
- Resolves: #8956
|
|
- Resolves: #8852
|
|
In case of the openvpn process being off, if we are restarting it we'll
report the status as 'starting'.
|
|
Right now we are trying to restart openvpn every 2 seconds, for ever (or
until the user turns down the VPN). Maybe we can be more smart making
the retries longer with time.
- Resolves: #8049
|
|
|
|
We were allways trying to reconnect for ever.
|
|
|
|
Some reordering, and general cleanup of options.
Some of the openvpn options are added now by bitmask-root.
- Resolves: #8948
|
|
|
|
this was producing a bug with parsing options in a recent enough
openvpn.
- Resolves: #8945
|
