| Age | Commit message (Collapse) | Author | Files | Lines |
|
When infra has deployed these block lists to the relays,
this setting will allow blocking social media domains
directly with the app
|
|
|
|
|
|
|
|
To be able to more easily re-use `get_filtered_relays` from other
modules, such as `custom_lists`, the function was to the module level.
|
|
Create meta type for pretty printing `GeographicLocationConstraint`
which is used for adding long country/city names to the output of the
`custom-list` cli command.
|
|
If the user wants to print a single list using `mullvad custom-list list
<name>`, the name of the list does not need to be part of the pretty print.
|
|
Re-arrange most of the subcommands of `mullvad custom-list` to decrease
clutter. This includes both re-ordering the different subcommands as
well as moving some subcommands to a new umbrella subcommand `mullvad
custom-list edit`.
The subcommands under `mullvad custom-list edit` operate on a single
custom list, i.e. appending to/renaming/deleting from a custom list.
The other subcommands under `mullvad custom-list` operate on the global
set of lists instead.
|
|
`mullvad custom-list list` now optionally takes an argument: A name of a
custom list to retrieve.
|
|
|
|
|
|
|
|
Bump the settings version. Add code for migrating settings to new
version since it is now not backwards compatible.
Refactor LocationConstraint and related types to be more lean.
Cleanup issues and fix formatting.
Refactor LocationConstraint and add migration code
|
|
Add necessary android support to allow it to not crash due to interface
changes. Format the code, remove redundant async functions, fix android issues
related to not having to use a Vec to store the custom lists and a
string as an id. Fix unit tests.
|
|
Create the basic features outside of rename for custom lists and route
these to the daemon. Persist custom lists in settings.
Has basic custom list features done, adds errors.
Adds reconnect in the case where a selected custom list is modified.
|
|
Add the same location constraint logic as `relay set location` to the
bridge location constraint for the `bridge set location` command. This
implies that the relay selection for both work in the same way.
|
|
|
|
Add the same location constraint logic as `relay set location` to the
entry location constraint for multihop. This implies that the relay
selection for both work in the same way.
|
|
The `set location` command now takes a hostname and figures the country
and city out. This is identical to how the (now deprecated) `mullvad
relay set hostname` used to work.
The `set location` command will try to resolve country code first, but
if that fails we now fall back to trying to resolve a relay by hostname
first.
Update the help message (long & short) to cover this new use case.
|
|
|
|
`mullvad account get` will print the old account number, even when the
device has revoked.
|
|
If the user is *not* logged in to an active account, we will from now on
issue a warning if they try to connect to a relay using `mullvad-cli`.
Previously, we would silently just start blocking all internet traffic.
This is well and good, as this is mandated by the state machine model.
The huge issue is that the user was unaware about the current status of
their connection without running further CLI commands or checking the
GUI. As this is to be considered a frustrating edge case, we might as
well try to help the user, since they can't look for answers on the
world wide web.
|
|
Previously, if `mullvad-cli` could not establish a connection to
`mullvad-daemon` for any reason, running `mullvad version` would not
print any version information whatsoever. Now we do print the current
build version of `mullvad-app`, which may or may not be in sync with the
installed version of `mullvad-daemon`.
We use the `mullvad-version` crate to figure out an appropriate response
in case `mullvad-daemon` is down.
|
|
|
|
|
|
|
|
|
|
|
|
the builder
|
|
|
|
Signed-off-by: Alexander Seiler <seileralex@gmail.com>
|
|
|
|
|
|
We still don't expose it in the UI. But we are now using the supposedly
stable endpoint on the servers. It has worked really well so far,
so we can probably be a bit less alarmist about it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This commit tries to manually fix the clippy warnings that are fairly
straightforward and do not have rippling effects on the codebase nor
have a very high chance of causing bugs.
|
|
|
|
|