package/{chrony, ntp, openntpd}: turn off DNSSEC validation
PATCH 1/1 package/{chrony, ntp, openntpd}: turn off DNSSEC validation
We have a chicken and egg problem: validation of DNSSEC signatures doesn't work without a correct clock, but to set the correct clock we need to contact NTP servers which requires resolving a hostname, which would normally require DNSSEC validation.
Let's break the cycle by excluding NTP hostname resolution from validation for now.
Details:
https://github.com/systemd/systemd/commit/abf4e5c1d3ad767bc0ed67883e8e4d916af095ec
--- package/chrony/chrony.service | 4 ++++ package/ntp/ntpd.service | 4 ++++ package/openntpd/ntpd.service | 4 ++++ 3 files changed, 12 insertions(+)
package/chrony/chrony.service +4 -0
@@ -4,6 +4,10 @@ After=syslog.target network.target Conflicts=systemd-timesyncd.service [Service] +# Turn off DNSSEC validation for hostname look-ups, since those need the +# correct time to work, but we likely won't acquire that without NTP. Let's +# break this chicken-and-egg cycle here. +Environment=SYSTEMD_NSS_RESOLVE_VALIDATE=0 ExecStart=/usr/sbin/chronyd -n Restart=always
package/ntp/ntpd.service +4 -0
@@ -5,6 +5,10 @@ After=network.target [Service] Type=forking PIDFile=/run/ntpd.pid +# Turn off DNSSEC validation for hostname look-ups, since those need the +# correct time to work, but we likely won't acquire that without NTP. Let's +# break this chicken-and-egg cycle here. +Environment=SYSTEMD_NSS_RESOLVE_VALIDATE=0 ExecStart=/usr/sbin/ntpd -g -p /run/ntpd.pid [Install]
package/openntpd/ntpd.service +4 -0
@@ -5,6 +5,10 @@ Conflicts=systemd-timesyncd.service [Service] Type=simple +# Turn off DNSSEC validation for hostname look-ups, since those need the +# correct time to work, but we likely won't acquire that without NTP. Let's +# break this chicken-and-egg cycle here. +Environment=SYSTEMD_NSS_RESOLVE_VALIDATE=0 ExecStart=/usr/sbin/ntpd -s -d [Install]
Signature · 1 line
2.25.1
PATCH 1/1 package/{chrony, ntp, openntpd}: turn off DNSSEC validation
Quoted 11 lines · On Thu, 8 Jul 2021 05:16:27 -0600 James Hilliard <[email protected]>…
We have a chicken and egg problem: validation of DNSSEC signatures doesn't work without a correct clock, but to set the correct clock we need to contact NTP servers which requires resolving a hostname, which would normally require DNSSEC validation.
Let's break the cycle by excluding NTP hostname resolution from validation for now.
Details:
https://github.com/systemd/systemd/commit/abf4e5c1d3ad767bc0ed67883e8e4d916af095ec
Quoted 6 lines
Signed-off-by James Hilliard <[email protected]>--- package/chrony/chrony.service | 4 ++++ package/ntp/ntpd.service | 4 ++++ package/openntpd/ntpd.service | 4 ++++ 3 files changed, 12 insertions(+)
I'm not an expert in this area, but the explanation seems sensible, and nobody complained so far, so I've applied to master. Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"James" == James Hilliard <[email protected]> writes:
We have a chicken and egg problem: validation of DNSSEC signatures doesn't work without a correct clock, but to set the correct clock we need to contact NTP servers which requires resolving a hostname, which would normally require DNSSEC validation.
Quoted 7 lines
Let's break the cycle by excluding NTP hostname resolution from validation for now.
Details:
https://github.com/systemd/systemd/commit/abf4e5c1d3ad767bc0ed67883e8e4d916af095ecSigned-off-by James Hilliard <[email protected]>
Committed to 2021.02.x and 2021.05.x, thanks.
Signature · 5 lines
Bye, Peter Korsgaard _______________________________________________ buildroot mailing list [email protected] http://lists.busybox.net/mailman/listinfo/buildroot