mullvadvpn - The Mullvad VPN client app for desktop and mobile

Age	Commit message (Collapse)	Author	Files	Lines
2021-12-14	Fix some cargo doc warnings	David Lönnhager	1	-1/+1

2021-11-29	Reformat code without blank_lines_upper_bound = 2	Linus Färnstrand	3	-9/+0

2021-09-15	Fix Rust nightly errors	David Lönnhager	1	-24/+4

2021-08-09	Always disable DNS over TLS in systemd-resolved	Emīls	1	-0/+28

2021-06-21	Fix unused borrow	David Lönnhager	1	-2/+2

2021-06-09	Work around issue where systemd-resolved only replaces a single existing DNS ↵	David Lönnhager	1	-1/+28
	server on an interface
2021-06-09	Fix D-Bus errors by using a separate connection for the route monitor	David Lönnhager	1	-0/+11

2021-06-09	Infer and monitor interfaces for DNS config	David Lönnhager	1	-17/+139

2021-03-26	Fix deadlock in systemd-resolved	Emīls	1	-5/+9

2021-03-02	Watch DNS config changes in systemd-resolved	Emīls	3	-0/+411
	Certain NM versions will overwrite systemd-resovled config when they're reapplying existing config, this can be invoked `nmcli general reload dns-full` or by receiving a new DHCP lease. NM will just wipe the config for interfaces it doesn't have the config for in systemd-resolved, and since our daemon prefers systemd-resolved over NM, our config would be wiped. To fix this, I've changed the systemd-resolved DNS code to listen to changes to the global DNS config and reapply the tunnel interface DNS config if it's changed in any way. To better seperate the conecrns, the systemd-resolved DBus specific code was moved to the `talpid-dbus` crate, and the DNS code that manages the state and applies changes remains in `talpid-core`. One other solution that was considered was to just prefer NM over systemd-resolved, and we already kind of could do that, but the coming NM versions (1.28 and up) seem to not be able to manage DNS via it's own /etc/resolv.conf.
2021-03-01	Stop using NM if it's too new	Emīls	1	-18/+64

2021-01-12	Expose NM version	Emīls	1	-4/+8

2021-01-12	Add talpid-dbus crate	Emīls	2	-0/+731