2.2.1.2 allways fails cause systemd-timesyncd isn't detected correctly
arctic-alpaca opened this issue · 0 comments
arctic-alpaca commented
Hi,
check 2.2.1.2 Ensure systemd-timesyncd is configured (Not Scored)
fails even though systemd-timesyncd
is enabled since the is_service_enabled
function doesn't work with systemd-timesyncd
.
According to the CIS Debian 10 Benchmark, systemctl is-enabled systemd-timesyncd.service
is the correct / a working check. This should return enabled
.
The output of timedatectl status
I get on my system isn't consistent with what's written in the benchmark.
Benchmark:
Local time: Tue 2019-06-04 15:40:45 EDT
Universal time: Tue 2019-06-04 19:40:45 UTC
RTC time: Tue 2019-06-04 19:40:45
Time zone: America/New_York (EDT, -0400)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2019-03-10 01:59:59 EST
Sun 2019-03-10 03:00:00 EDT
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2019-11-03 01:59:59 EDT
Sun 2019-11-03 01:00:00 EST
My System (up to date Debian 10)
Local time: Wed 2021-04-07 20:57:41 CEST
Universal time: Wed 2021-04-07 18:57:41 UTC
RTC time: Wed 2021-04-07 18:57:42
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no