| Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Co-authored-by: Sebastian Holmin <sebastian.holmin@mullvad.net>
|
|
Co-authored-by: Markus Pettersson <markus.pettersson@mullvad.net>
|
|
|
|
|
|
|
|
I ran `cargo doc` and fixed as many broken links as I could find.
|
|
|
|
Implement a system built on 'queries' for selecting appropriate relays.
A query is a set of constraints which dictates which relay(s) that *can*
be chosen by the relay selector.
The user's settings can naturally be expressed as a query. The semantics
of merging two queries in a way that always prefer user settings is
defined by the new `Intersection` trait.
Split `mullvad-relay-selector` into several modules:
- `query.rs`: Definition of a query on different types of relays. This
module is integral to the new API of `mullvad-relay-selector`
- `matcher.rs`: Logic for filtering out candidate relays based on a
query.
- `detailer.rs`: Logic for deriving connection details for the selected
relay.
- `tests/`: Integration tests for the new relay selector. These tests
only use the public APIs of `RelaySelector` and make sure that the
output matches the expected output in different scenarios.
|
|
`err_derive` is unmaintained and will probably stop working with rust
edition 2024. `thiserror` is almost a drop-in replacement. This commit
simply replaces all occurences of `derive(err_derive::Error)` with
`derive(thiserror::Error)` and fixes the attributes, but the Error and
Display impls should be identical.
|
|
Move `mullvad-relay-selector::relay_updater` to the `mullvad-daemon`.
The implications of this is that `mullvad-relay-selector` can drop the
dependency on both `mullvad-api` and `tokio`, which brings down the
total amount of dependencies when running a simple `Cargo check` from
250+ down to a mere 75. :-)
|
|
|
|
|
|
This PR has a couple of different purposes
- Allow users to use socks5 local proxies with the CLI without
having to be root nor use split-tunneling. This only works for
OpenVPN.
- Unify the types used by different proxy parts of the codebase,
such as the Access Methods as well as some already existing
OpenVPN proxy code.
This PR changes the firewall on all desktop platforms as well as changes
the routing table slightly on MacOS and Windows.
On Linux the firewall code is modified to apply the appropriate firewall
marks to all packages that go to a remote endpoint corresponding to the
remote part of a local socks5 proxy. The firewall marks will allow the
routing to be done without having to modify the routing table.
On MacOS and Windows the routing table is modified to allow packages to
go to that same endpoint to pass outside the VPN tunnel, it will
additionally punch a hole in the firewall.
The PR also migrates the settings file from version 7 to version 8 in order
to properly and neatly unify Proxy related types.
Finally it provides some slight extensions to the gRPC interface in
order to allow for control over the custom proxy settings.
|
|
|
|
|
|
There are currently only two ports, so this only simplifies the logic
but makes no practical difference
|
|
and other vestiges
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To align more with the upcoming standardizations within the Rust
ecosystem which started with the release of `1.70.0` and the inevitable
deprecation of `lazy_static`.
|
|
Since RelaySelector::get_obfuscator() is only ever called from tests, it
only makes sense to only compile it when testing.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Use a potential value between 0 and 1 provided by the API version check
to decide if the Windows client should use WireGuard or OpenVpn.
This decision is then persisted in the settings in the form of a random
value between 0 and 1 where if the value is higher than the value
provided by the API the client will use OpenVpn. If there is no value
provided by the API then the client will use WireGuard as the migration
has concluded.
|
|
|
|
|
|
|