Petr Menšík 6335e9de6a dns/dnsmasq: do not use --dnssec-proxy by default ... dnsmasq since 2.80 properly forwards all incoming queries with DO bit set. That ensures even if the dnsmasq does not do validation, it will always serve all DNSSEC records if the upstream server provides them. Regardless local validation is enabled or disabled, it will always offer all data required for validation to its clients. But does not set AD bit on local responses unless it did the actual validation itself. In case users trust their connection to validating DNS server, they would have to declare it by adding dnssec-proxy option to dnsmasq conf.d directory. Because there is no negated no-dnssec-proxy, it cannot be turned off. I think there is no good reason to be on for all cases and it would be possible to enable it if still wanted. Move the decision to the user. That makes it conform with RFC 4035, paragraph 3.2.3. Signed-off-by: Petr Menšík <pemensik@redhat.com> https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1639		2023-06-07 21:46:04 +02:00
..
nm-dns-dnsmasq.c	dns/dnsmasq: do not use --dnssec-proxy by default	2023-06-07 21:46:04 +02:00
nm-dns-dnsmasq.h	all: use _NM_G_TYPE_CHECK_INSTANCE_CAST() for internal uses	2022-12-16 10:55:03 +01:00
nm-dns-manager.c	dns: refactor domain_is_valid() to combine #if blocks	2023-05-02 11:42:55 +02:00
nm-dns-manager.h	core,libnm: move enum NMDnsIPConfigType	2023-02-07 13:46:14 +01:00
nm-dns-plugin.c	dns: add "update-pending" state to NMDnsPlugin	2022-04-15 09:04:29 +02:00
nm-dns-plugin.h	all: use _NM_G_TYPE_CHECK_INSTANCE_CAST() for internal uses	2022-12-16 10:55:03 +01:00
nm-dns-systemd-resolved.c	all: use nm_g_array_first()/nm_g_array_first_p() where suitable	2022-12-09 09:15:53 +01:00
nm-dns-systemd-resolved.h	all: use _NM_G_TYPE_CHECK_INSTANCE_CAST() for internal uses	2022-12-16 10:55:03 +01:00