summaryrefslogtreecommitdiffhomepage
path: root/talpid-dbus/src
AgeCommit message (Collapse)AuthorFilesLines
2025-09-08Fix lint `clippy::implicit_clone`Markus Pettersson1-2/+2
2025-07-15Fix `collapsible_if` clippy lintMarkus Pettersson1-4/+4
2025-07-10Run `cargo fmt`Sebastian Holmin3-6/+8
2025-03-18Remove needsless cloning of objectsLinus Färnstrand1-2/+1
2025-01-14Fix new `clippy` warningsMarkus Pettersson1-2/+1
2024-09-02Fix rustc nightly error: `elided lifetime has a name`Markus Pettersson1-3/+3
2024-08-27Use std LazyLock instead of once_cell LazyDavid Lönnhager2-6/+11
2024-06-14Adapt to new never type fallback by explicitly stating unit typesLinus Färnstrand2-3/+6
2024-04-03Enable single-use-lifetimes rustc lintLinus Färnstrand1-13/+10
Removes superfluous lifetime definitions. Simplifying the code
2024-02-27Replace err_derive with thiserrorJoakim Hulthe3-50/+47
`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.
2024-02-19Fix redundant importsDavid Lönnhager1-1/+0
2024-01-04Add workspace level lintsLinus Färnstrand1-1/+1
2023-08-04Replace all use of `lazy_static` with `once_cell`Markus Pettersson2-8/+7
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`.
2023-03-27Fix many typosAlexander Seiler1-1/+1
Signed-off-by: Alexander Seiler <seileralex@gmail.com>
2022-11-07Split up talpid-coreEmīls Piņķis1-0/+6
2022-09-27Fix clippy complaintsEmīls Piņķis1-4/+4
2022-09-21Add systemd module to talpid-dbusEmīls Piņķis2-0/+68
2022-06-21Fix the large majority of clippy warningsJonathan2-6/+5
This commit fixes most of the remaining clippy warnings in the codebase. These warnings were the more semantically difficult ones to fix. There are some warnings that remain from the rebase that will be fixed in the upcoming PR.
2022-06-14Manually fix the simpler non-semantic clippy warnsJonathan1-1/+1
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.
2022-06-13Perform a clippy --fixjonathan2-11/+11
This is a giant commit which performs only a clippy --fix. Auditing can happen in two ways, either by reading every line or by running a `cargo clippy --fix` on the previous commit and make sure that the result is the same.
2022-05-13Fix small typoEmīls1-2/+2
2022-01-11Use ": " as delimiter instead of " - " between messages and valueLinus Färnstrand2-6/+6
2021-12-14Fix some cargo doc warningsDavid Lönnhager1-1/+1
2021-11-29Reformat code without blank_lines_upper_bound = 2Linus Färnstrand3-9/+0
2021-09-15Fix Rust nightly errorsDavid Lönnhager1-24/+4
2021-08-09Always disable DNS over TLS in systemd-resolvedEmīls1-0/+28
2021-06-21Fix unused borrowDavid Lönnhager1-2/+2
2021-06-09Work around issue where systemd-resolved only replaces a single existing DNS ↵David Lönnhager1-1/+28
server on an interface
2021-06-09Fix D-Bus errors by using a separate connection for the route monitorDavid Lönnhager1-0/+11
2021-06-09Infer and monitor interfaces for DNS configDavid Lönnhager1-17/+139
2021-03-26Fix deadlock in systemd-resolvedEmīls1-5/+9
2021-03-02Watch DNS config changes in systemd-resolvedEmīls3-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-01Stop using NM if it's too newEmīls1-18/+64
2021-01-12Expose NM versionEmīls1-4/+8
2021-01-12Add talpid-dbus crateEmīls2-0/+731