Repository navigation
Conversation
|
I tested the As an unprivileged user, Measured locally: $ resolvectl statistics >/dev/null
# opens a polkit dialog and waits
$ resolvectl status >/dev/null
# exits 0 immediately, no polkit authorization event
So on this configuration the change fixes both the DNSSEC parsing and an |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
summary
this pr improves the dnssec detection logic in the `netw-2706` test to support newer versions of `systemd-resolved` (systemd 250 and later).
problem
the current implementation relies on `resolvectl --statistics`, which only provides statistical counters and does not reliably indicate whether dnssec is active for the current network interfaces. furthermore, the previous `awk` parsing logic fails on newer output formats like `dnssec=yes/supported`.
changes
note for maintainers
i am a japanese user and am using a machine translator to write this. i apologize for any unnatural phrasing. i have verified this fix on my local environment, and it now correctly returns `yes`.
verified result
miikun95, miikun95@miikun95.net