2 # SPDX-License-Identifier: LGPL-2.1-or-later
3 # shellcheck disable=SC2016
6 # shellcheck source=test/units/util.sh
7 .
"$(dirname "$0")"/util.sh
9 systemctl log-level debug
10 export SYSTEMD_LOG_LEVEL
=debug
14 # We can't really test time, critical-chain and plot verbs here, as
15 # the testsuite service is a part of the boot transaction, so let's assume
18 systemd-analyze
time ||
:
19 systemd-analyze critical-chain ||
:
22 systemd-run
--wait --user --pipe -M testuser@.
host systemd-analyze blame
24 systemd-analyze plot
>/dev
/null ||
:
25 systemd-analyze plot
--json=pretty
>/dev
/null ||
:
26 systemd-analyze plot
--json=short
>/dev
/null ||
:
27 systemd-analyze plot
--json=off
>/dev
/null ||
:
28 systemd-analyze plot
--json=pretty
--no-legend >/dev
/null ||
:
29 systemd-analyze plot
--json=short
--no-legend >/dev
/null ||
:
30 systemd-analyze plot
--json=off
--no-legend >/dev
/null ||
:
31 systemd-analyze plot
--table >/dev
/null ||
:
32 systemd-analyze plot
--table --no-legend >/dev
/null ||
:
33 # legacy/deprecated options (moved to systemctl, but still usable from analyze)
34 systemd-analyze log-level
35 systemd-analyze log-level
"$(systemctl log-level)"
36 systemd-analyze get-log-level
37 systemd-analyze set-log-level
"$(systemctl log-level)"
38 systemd-analyze log-target
39 systemd-analyze log-target
"$(systemctl log-target)"
40 systemd-analyze get-log-target
41 systemd-analyze set-log-target
"$(systemctl log-target)"
42 systemd-analyze service-watchdogs
43 systemd-analyze service-watchdogs
"$(systemctl service-watchdogs)"
45 systemd-analyze dot
>/dev
/null
46 systemd-analyze dot systemd-journald.service
>/dev
/null
47 systemd-analyze dot systemd-journald.service systemd-logind.service
>/dev
/null
48 systemd-analyze dot
--from-pattern="*" --from-pattern="*.service" systemd-journald.service
>/dev
/null
49 systemd-analyze dot
--to-pattern="*" --to-pattern="*.service" systemd-journald.service
>/dev
/null
50 systemd-analyze dot
--from-pattern="*.service" --to-pattern="*.service" systemd-journald.service
>/dev
/null
51 systemd-analyze dot
--order systemd-journald.service systemd-logind.service
>/dev
/null
52 systemd-analyze dot
--require systemd-journald.service systemd-logind.service
>/dev
/null
53 systemd-analyze dot
"systemd-*.service" >/dev
/null
54 (! systemd-analyze dot systemd-journald.service systemd-logind.service
"*" bbb ccc
)
56 # this should be rate limited to 10 calls in 10 minutes for unprivileged callers
58 runas testuser systemd-analyze dump systemd-journald.service
>/dev
/null
60 (! runas testuser systemd-analyze dump
>/dev
/null
)
61 # still limited after a reload
62 systemctl daemon-reload
63 (! runas testuser systemd-analyze dump
>/dev
/null
)
65 systemctl daemon-reexec
66 (! runas testuser systemd-analyze dump
>/dev
/null
)
67 # privileged call, so should not be rate limited
69 systemd-analyze dump systemd-journald.service
>/dev
/null
71 systemd-analyze dump
>/dev
/null
72 systemd-analyze dump
"*" >/dev
/null
73 systemd-analyze dump
"*.socket" >/dev
/null
74 systemd-analyze dump
"*.socket" "*.service" aaaaaaa ...
>/dev
/null
75 systemd-analyze dump systemd-journald.service
>/dev
/null
76 systemd-analyze malloc
>/dev
/null
77 (! systemd-analyze dump
"")
79 systemd-analyze unit-files
>/dev
/null
80 systemd-analyze unit-files systemd-journald.service
>/dev
/null
81 systemd-analyze unit-files
"*" >/dev
/null
82 systemd-analyze unit-files
"*" aaaaaa
"*.service" "*.target" >/dev
/null
83 systemd-analyze unit-files
--user >/dev
/null
84 systemd-analyze unit-files
--user "*" aaaaaa
"*.service" "*.target" >/dev
/null
86 systemd-analyze unit-paths
87 systemd-analyze unit-paths
--user
88 systemd-analyze unit-paths
--global
90 systemd-analyze exit-status
91 systemd-analyze exit-status STDOUT BPF
92 systemd-analyze exit-status
0 1 {63.
.65}
93 (! systemd-analyze exit-status STDOUT BPF
"hello*")
95 systemd-analyze capability
96 systemd-analyze capability cap_chown CAP_KILL
97 systemd-analyze capability
0 1 {30.
.32}
98 (! systemd-analyze capability cap_chown CAP_KILL
"hello*")
100 mkdir
-p /run
/systemd
/system
101 UNIT_NAME
="analyze-condition-$RANDOM.service"
102 cat >"/run/systemd/system/$UNIT_NAME" <<EOF
104 AssertPathExists=/etc/os-release
105 AssertEnvironment=!FOOBAR
106 ConditionKernelVersion=>1.0
107 ConditionPathExists=/etc/os-release
112 systemctl daemon-reload
113 systemd-analyze condition
--unit="$UNIT_NAME"
114 systemd-analyze condition
'ConditionKernelVersion = ! <4.0' \
115 'ConditionKernelVersion = >=3.1' \
116 'ConditionACPower=|false' \
117 'ConditionArchitecture=|!arm' \
118 'AssertPathExists=/etc/os-release'
119 (! systemd-analyze condition
'ConditionArchitecture=|!arm' 'AssertXYZ=foo')
120 (! systemd-analyze condition
'ConditionKernelVersion=<1.0')
121 (! systemd-analyze condition
'AssertKernelVersion=<1.0')
123 systemd-analyze syscall-filter
>/dev
/null
124 systemd-analyze syscall-filter @chown @sync
125 systemd-analyze syscall-filter @sync @sync @sync
126 (! systemd-analyze syscall-filter @chown @sync @foobar
)
127 # filesystems (requires libbpf support)
128 if systemctl
--version |
grep "+BPF_FRAMEWORK"; then
129 systemd-analyze filesystems
>/dev
/null
130 systemd-analyze filesystems @basic-api
131 systemd-analyze filesystems @basic-api @basic-api @basic-api
132 (! systemd-analyze filesystems @basic-api @basic-api @foobar @basic-api
)
135 systemd-analyze calendar
'*-2-29 0:0:0'
136 systemd-analyze calendar
--iterations=5 '*-2-29 0:0:0'
137 systemd-analyze calendar
'*-* *:*:*'
138 systemd-analyze calendar
--iterations=5 '*-* *:*:*'
139 systemd-analyze calendar
--iterations=50 '*-* *:*:*'
140 systemd-analyze calendar
--iterations=0 '*-* *:*:*'
141 systemd-analyze calendar
--iterations=5 '01-01-22 01:00:00'
142 systemd-analyze calendar
--base-time=yesterday
--iterations=5 '*-* *:*:*'
143 (! systemd-analyze calendar
--iterations=0 '*-* 99:*:*')
144 (! systemd-analyze calendar
--base-time=never
'*-* *:*:*')
145 (! systemd-analyze calendar
1)
146 (! systemd-analyze calendar
"")
148 systemd-analyze timestamp now
149 systemd-analyze timestamp
-- -1
150 systemd-analyze timestamp yesterday now tomorrow
151 (! systemd-analyze timestamp yesterday never tomorrow
)
152 (! systemd-analyze timestamp
1)
153 (! systemd-analyze timestamp
'*-2-29 0:0:0')
154 (! systemd-analyze timestamp
"")
156 systemd-analyze timespan
1
157 systemd-analyze timespan
1s
300s
'1year 0.000001s'
158 (! systemd-analyze timespan
1s
300s aaaaaa
'1year 0.000001s')
159 (! systemd-analyze timespan
-- -1)
160 (! systemd-analyze timespan
'*-2-29 0:0:0')
161 (! systemd-analyze timespan
"")
163 systemd-analyze cat-config systemd
/system.conf
>/dev
/null
164 systemd-analyze cat-config
/etc
/systemd
/system.conf
>/dev
/null
165 systemd-analyze cat-config systemd
/system.conf systemd
/journald.conf
>/dev
/null
166 systemd-analyze cat-config systemd
/system.conf foo
/bar systemd
/journald.conf
>/dev
/null
167 systemd-analyze cat-config foo
/bar
168 systemd-analyze cat-config
--tldr systemd
/system.conf
>/dev
/null
169 systemd-analyze cat-config
--tldr /etc
/systemd
/system.conf
>/dev
/null
170 systemd-analyze cat-config
--tldr systemd
/system.conf systemd
/journald.conf
>/dev
/null
171 systemd-analyze cat-config
--tldr systemd
/system.conf foo
/bar systemd
/journald.conf
>/dev
/null
172 systemd-analyze cat-config
--tldr foo
/bar
174 systemd-analyze security
175 systemd-analyze security
--json=off
176 systemd-analyze security
--json=pretty | jq
177 systemd-analyze security
--json=short | jq
179 if [[ ! -v ASAN_OPTIONS
]]; then
180 # check that systemd-analyze cat-config paths work in a chroot
182 mount
--bind / /tmp
/root
183 systemd-analyze cat-config systemd
/system-preset
>/tmp
/out1
184 chroot
/tmp
/root systemd-analyze cat-config systemd
/system-preset
>/tmp
/out2
189 mkdir
-p /tmp
/img
/usr
/lib
/systemd
/system
/
190 mkdir
-p /tmp
/img
/opt
/
192 touch /tmp
/img
/opt
/script0.sh
193 chmod +x
/tmp
/img
/opt
/script0.sh
195 cat <<EOF >/tmp/img/usr/lib/systemd/system/testfile.service
197 ExecStart = /opt/script0.sh
201 # Default behaviour is to recurse through all dependencies when unit is loaded
202 (! systemd-analyze verify
--root=/tmp
/img
/ testfile.service
)
204 # As above, recurses through all dependencies when unit is loaded
205 (! systemd-analyze verify
--recursive-errors=yes --root=/tmp
/img
/ testfile.service
)
207 # Recurses through unit file and its direct dependencies when unit is loaded
208 (! systemd-analyze verify
--recursive-errors=one
--root=/tmp
/img
/ testfile.service
)
212 # zero exit status since dependencies are ignored when unit is loaded
213 systemd-analyze verify
--recursive-errors=no
--root=/tmp
/img
/ testfile.service
215 rm /tmp
/img
/usr
/lib
/systemd
/system
/testfile.service
217 cat <<EOF >/tmp/testfile.service
222 ExecStart = echo hello
225 cat <<EOF >/tmp/testfile2.service
227 Requires = testfile.service
230 ExecStart = echo hello
233 # Zero exit status since no additional dependencies are recursively loaded when the unit file is loaded
234 systemd-analyze verify
--recursive-errors=no
/tmp
/testfile2.service
237 # Non-zero exit status since all associated dependencies are recursively loaded when the unit file is loaded
238 (! systemd-analyze verify
--recursive-errors=yes /tmp
/testfile2.service
)
241 rm /tmp
/testfile.service
242 rm /tmp
/testfile2.service
244 cat <<EOF >/tmp/sample.service
246 Description = A Sample Service
249 ExecStart = echo hello
253 # Zero exit status since no additional dependencies are recursively loaded when the unit file is loaded
254 systemd-analyze verify
--recursive-errors=no
/tmp
/sample.service
256 cat <<EOF >/tmp/testfile.service
258 ExecStart = echo hello
262 # Prevent regression from #13380 and #20859 where we can't verify hidden files
263 cp /tmp
/testfile.service
/tmp
/.testfile.service
265 systemd-analyze verify
/tmp
/.testfile.service
267 rm /tmp
/.testfile.service
269 # Alias a unit file's name on disk (see #20061)
270 cp /tmp
/testfile.service
/tmp
/testsrvc
272 (! systemd-analyze verify
/tmp
/testsrvc
)
274 systemd-analyze verify
/tmp
/testsrvc
:alias.service
276 # Zero exit status since the value used for comparison determine exposure to security threats is by default 100
277 systemd-analyze security
--offline=true
/tmp
/testfile.service
279 #The overall exposure level assigned to the unit is greater than the set threshold
280 (! systemd-analyze security
--threshold=90 --offline=true
/tmp
/testfile.service
)
282 # Ensure we print the list of ACLs, see https://github.com/systemd/systemd/issues/23185
283 systemd-analyze security
--offline=true
/tmp
/testfile.service |
grep -q -F "/dev/sda"
285 rm /tmp
/testfile.service
287 cat <<EOF >/tmp/img/usr/lib/systemd/system/testfile.service
289 ExecStart = echo hello
295 # The new overall exposure level assigned to the unit is less than the set thresholds
296 # Verifies that the --offline= option works with --root=
297 systemd-analyze security
--threshold=90 --offline=true
--root=/tmp
/img
/ testfile.service
299 # Added an additional "INVALID_ID" id to the .json to verify that nothing breaks when input is malformed
300 # The PrivateNetwork id description and weight was changed to verify that 'security' is actually reading in
301 # values from the .json file when required. The default weight for "PrivateNetwork" is 2500, and the new weight
302 # assigned to that id in the .json file is 6000. This increased weight means that when the "PrivateNetwork" key is
303 # set to 'yes' (as above in the case of testfile.service) in the content of the unit file, the overall exposure
304 # level for the unit file should decrease to account for that increased weight.
305 cat <<EOF >/tmp/testfile.json
306 {"UserOrDynamicUser":
307 {"description_bad": "Service runs as root user",
311 "SupplementaryGroups":
312 {"description_good": "Service has no supplementary groups",
313 "description_bad": "Service runs with supplementary groups",
314 "description_na": "Service runs as root, option does not matter",
319 {"description_good": "Service has no access to hardware devices",
320 "description_bad": "Service potentially has access to hardware devices",
325 {"description_good": "Service cannot install system mounts",
326 "description_bad": "Service may install system mounts",
331 {"description_good": "Service doesn't have access to the host's network",
332 "description_bad": "Service has access to the host's network",
337 {"description_good": "Service has no access to other software's temporary files",
338 "description_bad": "Service has access to other software's temporary files",
343 {"description_good": "Service does not have access to other users",
344 "description_bad": "Service has access to other users",
348 "ProtectControlGroups":
349 {"description_good": "Service cannot modify the control group file system",
350 "description_bad": "Service may modify the control group file system",
354 "ProtectKernelModules":
355 {"description_good": "Service cannot load or read kernel modules",
356 "description_bad": "Service may load or read kernel modules",
360 "ProtectKernelTunables":
361 {"description_good": "Service cannot alter kernel tunables (/proc/sys, …)",
362 "description_bad": "Service may alter kernel tunables",
367 {"description_good": "Service cannot read from or write to the kernel log ring buffer",
368 "description_bad": "Service may read from or write to the kernel log ring buffer",
373 {"description_good": "Service cannot write to the hardware clock or system clock",
374 "description_bad": "Service may write to the hardware clock or system clock",
383 {"description_good": "Service cannot change system host/domainname",
384 "description_bad": "Service may change system host/domainname",
392 "RootDirectoryOrRootImage":
393 {"description_good": "Service has its own root directory/image",
394 "description_bad": "Service runs within the host's root directory",
399 {"description_good": "Service cannot change ABI personality",
400 "description_bad": "Service may change ABI personality",
404 "MemoryDenyWriteExecute":
405 {"description_good": "Service cannot create writable executable memory mappings",
406 "description_bad": "Service may create writable executable memory mappings",
411 {"description_good": "Service processes cannot acquire new privileges",
412 "description_bad": "Service processes may acquire new privileges",
416 "CapabilityBoundingSet_CAP_SYS_ADMIN":
417 {"description_good": "Service has no administrator privileges",
418 "description_bad": "Service has administrator privileges",
422 "CapabilityBoundingSet_CAP_SET_UID_GID_PCAP":
423 {"description_good": "Service cannot change UID/GID identities/capabilities",
424 "description_bad": "Service may change UID/GID identities/capabilities",
428 "CapabilityBoundingSet_CAP_SYS_PTRACE":
429 {"description_good": "Service has no ptrace() debugging abilities",
430 "description_bad": "Service has ptrace() debugging abilities",
434 "CapabilityBoundingSet_CAP_SYS_TIME":
435 {"description_good": "Service processes cannot change the system clock",
436 "description_bad": "Service processes may change the system clock",
440 "CapabilityBoundingSet_CAP_NET_ADMIN":
441 {"description_good": "Service has no network configuration privileges",
442 "description_bad": "Service has network configuration privileges",
446 "CapabilityBoundingSet_CAP_SYS_RAWIO":
447 {"description_good": "Service has no raw I/O access",
448 "description_bad": "Service has raw I/O access",
452 "CapabilityBoundingSet_CAP_SYS_MODULE":
453 {"description_good": "Service cannot load kernel modules",
454 "description_bad": "Service may load kernel modules",
458 "CapabilityBoundingSet_CAP_AUDIT":
459 {"description_good": "Service has no audit subsystem access",
460 "description_bad": "Service has audit subsystem access",
464 "CapabilityBoundingSet_CAP_SYSLOG":
465 {"description_good": "Service has no access to kernel logging",
466 "description_bad": "Service has access to kernel logging",
470 "CapabilityBoundingSet_CAP_SYS_NICE_RESOURCE":
471 {"description_good": "Service has no privileges to change resource use parameters",
472 "description_bad": "Service has privileges to change resource use parameters",
476 "CapabilityBoundingSet_CAP_MKNOD":
477 {"description_good": "Service cannot create device nodes",
478 "description_bad": "Service may create device nodes",
482 "CapabilityBoundingSet_CAP_CHOWN_FSETID_SETFCAP":
483 {"description_good": "Service cannot change file ownership/access mode/capabilities",
484 "description_bad": "Service may change file ownership/access mode/capabilities unrestricted",
488 "CapabilityBoundingSet_CAP_DAC_FOWNER_IPC_OWNER":
489 {"description_good": "Service cannot override UNIX file/IPC permission checks",
490 "description_bad": "Service may override UNIX file/IPC permission checks",
494 "CapabilityBoundingSet_CAP_KILL":
495 {"description_good": "Service cannot send UNIX signals to arbitrary processes",
496 "description_bad": "Service may send UNIX signals to arbitrary processes",
500 "CapabilityBoundingSet_CAP_NET_BIND_SERVICE_BROADCAST_RAW":
501 {"description_good": "Service has no elevated networking privileges",
502 "description_bad": "Service has elevated networking privileges",
506 "CapabilityBoundingSet_CAP_SYS_BOOT":
507 {"description_good": "Service cannot issue reboot()",
508 "description_bad": "Service may issue reboot()",
512 "CapabilityBoundingSet_CAP_MAC":
513 {"description_good": "Service cannot adjust SMACK MAC",
514 "description_bad": "Service may adjust SMACK MAC",
518 "CapabilityBoundingSet_CAP_LINUX_IMMUTABLE":
519 {"description_good": "Service cannot mark files immutable",
520 "description_bad": "Service may mark files immutable",
524 "CapabilityBoundingSet_CAP_IPC_LOCK":
525 {"description_good": "Service cannot lock memory into RAM",
526 "description_bad": "Service may lock memory into RAM",
530 "CapabilityBoundingSet_CAP_SYS_CHROOT":
531 {"description_good": "Service cannot issue chroot()",
532 "description_bad": "Service may issue chroot()",
536 "CapabilityBoundingSet_CAP_BLOCK_SUSPEND":
537 {"description_good": "Service cannot establish wake locks",
538 "description_bad": "Service may establish wake locks",
542 "CapabilityBoundingSet_CAP_WAKE_ALARM":
543 {"description_good": "Service cannot program timers that wake up the system",
544 "description_bad": "Service may program timers that wake up the system",
548 "CapabilityBoundingSet_CAP_LEASE":
549 {"description_good": "Service cannot create file leases",
550 "description_bad": "Service may create file leases",
554 "CapabilityBoundingSet_CAP_SYS_TTY_CONFIG":
555 {"description_good": "Service cannot issue vhangup()",
556 "description_bad": "Service may issue vhangup()",
560 "CapabilityBoundingSet_CAP_SYS_PACCT":
561 {"description_good": "Service cannot use acct()",
562 "description_bad": "Service may use acct()",
571 {"description_good": "Service doesn't share key material with other services",
572 "description_bad": "Service shares key material with other service",
577 {"description_good": "Service has restricted access to process tree(/proc hidepid=)",
578 "description_bad": "Service has full access to process tree(/proc hidepid=)",
583 {"description_good": "Service has no access to non-process/proc files(/proc subset=)",
584 "description_bad": "Service has full access to non-process/proc files(/proc subset=)",
589 {"description_good": "Service child processes cannot alter service state",
590 "description_bad": "Service child processes may alter service state",
595 {"description_good": "Service user cannot leave SysV IPC objects around",
596 "description_bad": "Service user may leave SysV IPC objects around",
597 "description_na": "Service runs as root, option does not apply",
602 {"description_good": "Service does not maintain its own delegated control group subtree",
603 "description_bad": "Service maintains its own delegated control group subtree",
608 {"description_good": "Service realtime scheduling access is restricted",
609 "description_bad": "Service may acquire realtime scheduling",
614 {"description_good": "SUID/SGIDfilecreationbyserviceisrestricted",
615 "description_bad": "ServicemaycreateSUID/SGIDfiles",
619 "RestrictNamespaces_user":
620 {"description_good": "Servicecannotcreateusernamespaces",
621 "description_bad": "Servicemaycreateusernamespaces",
625 "RestrictNamespaces_mnt":
626 {"description_good": "Service cannot create file system namespaces",
627 "description_bad": "Service may create file system namespaces",
631 "RestrictNamespaces_ipc":
632 {"description_good": "Service cannot create IPC namespaces",
633 "description_bad": "Service may create IPC namespaces",
637 "RestrictNamespaces_pid":
638 {"description_good": "Service cannot create process namespaces",
639 "description_bad": "Service may create process namespaces",
643 "RestrictNamespaces_cgroup":
644 {"description_good": "Service cannot create cgroup namespaces",
645 "description_bad": "Service may create cgroup namespaces",
649 "RestrictNamespaces_net":
650 {"description_good": "Service cannot create network namespaces",
651 "description_bad": "Service may create network namespaces",
655 "RestrictNamespaces_uts":
656 {"description_good": "Service cannot create hostname namespaces",
657 "description_bad": "Service may create hostname namespaces",
661 "RestrictAddressFamilies_AF_INET_INET6":
662 {"description_good": "Service cannot allocate Internet sockets",
663 "description_bad": "Service may allocate Internet sockets",
667 "RestrictAddressFamilies_AF_UNIX":
668 {"description_good": "Service cannot allocate local sockets",
669 "description_bad": "Service may allocate local sockets",
673 "RestrictAddressFamilies_AF_NETLINK":
674 {"description_good": "Service cannot allocate netlink sockets",
675 "description_bad": "Service may allocate netlink sockets",
679 "RestrictAddressFamilies_AF_PACKET":
680 {"description_good": "Service cannot allocate packet sockets",
681 "description_bad": "Service may allocate packet sockets",
685 "RestrictAddressFamilies_OTHER":
686 {"description_good": "Service cannot allocate exotic sockets",
687 "description_bad": "Service may allocate exotic sockets",
691 "SystemCallArchitectures":
695 "SystemCallFilter_swap":
699 "SystemCallFilter_obsolete":
703 "SystemCallFilter_clock":
707 "SystemCallFilter_cpu_emulation":
711 "SystemCallFilter_debug":
715 "SystemCallFilter_mount":
719 "SystemCallFilter_module":
723 "SystemCallFilter_raw_io":
727 "SystemCallFilter_reboot":
731 "SystemCallFilter_privileged":
735 "SystemCallFilter_resources":
747 "AmbientCapabilities":
748 {"description_good": "Service process does not receive ambient capabilities",
749 "description_bad": "Service process receives ambient capabilities",
760 # Reads in custom security requirements from the parsed .json file and uses these for comparison
761 systemd-analyze security
--threshold=90 --offline=true \
762 --security-policy=/tmp
/testfile.json \
763 --root=/tmp
/img
/ testfile.service
765 # The strict profile adds a lot of sanboxing options
766 systemd-analyze security
--threshold=25 --offline=true \
767 --security-policy=/tmp
/testfile.json \
769 --root=/tmp
/img
/ testfile.service
771 # The trusted profile doesn't add any sanboxing options
772 (! systemd-analyze security
--threshold=25 --offline=true \
773 --security-policy=/tmp
/testfile.json \
774 --profile=/usr
/lib
/systemd
/portable
/profile
/trusted
/service.conf \
775 --root=/tmp
/img
/ testfile.service
)
777 (! systemd-analyze security
--threshold=50 --offline=true \
778 --security-policy=/tmp
/testfile.json \
779 --root=/tmp
/img
/ testfile.service
)
781 rm /tmp
/img
/usr
/lib
/systemd
/system
/testfile.service
783 if systemd-analyze
--version |
grep -q -F "+ELFUTILS"; then
784 systemd-analyze inspect-elf
--json=short
/lib
/systemd
/systemd |
grep -q -F '"elfType":"executable"'
787 systemd-analyze
--threshold=90 security systemd-journald.service
792 output
=$
(systemd-analyze security
--offline="${2?}" "${3?}" |
grep -F 'SystemCallFilter=')
793 assert_in
"System call ${1?} list" "$output"
794 assert_in
"[+✓] SystemCallFilter=~@swap" "$output"
795 assert_in
"[+✓] SystemCallFilter=~@resources" "$output"
796 assert_in
"[+✓] SystemCallFilter=~@reboot" "$output"
797 assert_in
"[+✓] SystemCallFilter=~@raw-io" "$output"
798 assert_in
"[-✗] SystemCallFilter=~@privileged" "$output"
799 assert_in
"[+✓] SystemCallFilter=~@obsolete" "$output"
800 assert_in
"[+✓] SystemCallFilter=~@mount" "$output"
801 assert_in
"[+✓] SystemCallFilter=~@module" "$output"
802 assert_in
"[+✓] SystemCallFilter=~@debug" "$output"
803 assert_in
"[+✓] SystemCallFilter=~@cpu-emulation" "$output"
804 assert_in
"[-✗] SystemCallFilter=~@clock" "$output"
807 export -n SYSTEMD_LOG_LEVEL
809 mkdir
-p /run
/systemd
/system
810 cat >/run
/systemd
/system
/allow-list.service
<<EOF
813 SystemCallFilter=@system-service
814 SystemCallFilter=~@resources:ENOANO @privileged
815 SystemCallFilter=@clock
818 cat >/run
/systemd
/system
/deny-list.service
<<EOF
821 SystemCallFilter=~@known
822 SystemCallFilter=@system-service
823 SystemCallFilter=~@resources:ENOANO @privileged
824 SystemCallFilter=@clock
827 systemctl daemon-reload
829 check allow
yes /run
/systemd
/system
/allow-list.service
830 check allow no allow-list.service
831 check deny
yes /run
/systemd
/system
/deny-list.service
832 check deny no deny-list.service
834 output
=$
(systemd-run
-p "SystemCallFilter=@system-service" -p "SystemCallFilter=~@resources:ENOANO @privileged" -p "SystemCallFilter=@clock" sleep 60 2>&1)
835 name
=$
(echo "$output" |
awk '{ print $4 }' | cut
-d';' -f1)
837 check allow
yes /run
/systemd
/transient
/"$name"
838 check allow no
"$name"
840 output
=$
(systemd-run
-p "SystemCallFilter=~@known" -p "SystemCallFilter=@system-service" -p "SystemCallFilter=~@resources:ENOANO @privileged" -p "SystemCallFilter=@clock" sleep 60 2>&1)
841 name
=$
(echo "$output" |
awk '{ print $4 }' | cut
-d';' -f1)
843 check deny
yes /run
/systemd
/transient
/"$name"
844 check deny no
"$name"
846 # Let's also test the "image-policy" verb
848 systemd-analyze image-policy
'*' 2>&1 |
grep -q -F "Long form: =verity+signed+encrypted+unprotected+unused+absent"
849 systemd-analyze image-policy
'-' 2>&1 |
grep -q -F "Long form: =unused+absent"
850 systemd-analyze image-policy
'home=encrypted:usr=verity' 2>&1 |
grep -q -F "Long form: usr=verity:home=encrypted:=unused+absent"
851 systemd-analyze image-policy
'home=encrypted:usr=verity' 2>&1 |
grep -q -e '^home \+encrypted \+'
852 systemd-analyze image-policy
'home=encrypted:usr=verity' 2>&1 |
grep -q -e '^usr \+verity \+'
853 systemd-analyze image-policy
'home=encrypted:usr=verity' 2>&1 |
grep -q -e '^root \+ignore \+'
854 systemd-analyze image-policy
'home=encrypted:usr=verity' 2>&1 |
grep -q -e '^usr-verity \+unprotected \+'
856 (! systemd-analyze image-policy
'doedel')
858 # Output is very hard to predict, but let's run it for coverage anyway
860 systemd-analyze pcrs
--json=pretty
861 systemd-analyze pcrs
14 7 0 ima
863 systemd-analyze log-level info