Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

persist state for wicked, chrony, and systemd #970

Merged
merged 6 commits into from
Jul 9, 2020

Conversation

bcressey
Copy link
Contributor

@bcressey bcressey commented Jul 7, 2020

Issue number:
#248 , #249 , #250

Description of changes:
Confine chrony, wicked, and dbus-broker via SELinux policy; move DHCP leases and clock measurements back to persistent storage. Also persist the journal and the random seed.

Testing done:
No AVC denials logged in dmesg or in the journal.

Processes are labeled as expected.

system_u:system_r:bus_t:s0         3023 ?        Ss     0:00 /usr/bin/dbus-broker-launch --scope system
system_u:system_r:bus_t:s0         3067 ?        S      0:00 dbus-broker --log 4 --controller 9 --machine-id 990978842db9412194d093dc75af968b --max-
system_u:system_r:network_t:s0     3124 ?        Ss     0:00 /x86_64-bottlerocket-linux-gnu/sys-root/usr/libexec/wicked/bin/wickedd-auto4 --systemd
system_u:system_r:network_t:s0     3136 ?        Ss     0:00 /x86_64-bottlerocket-linux-gnu/sys-root/usr/libexec/wicked/bin/wickedd-dhcp4 --systemd
system_u:system_r:network_t:s0     3155 ?        Ss     0:00 /x86_64-bottlerocket-linux-gnu/sys-root/usr/libexec/wicked/bin/wickedd-dhcp6 --systemd
system_u:system_r:network_t:s0     3218 ?        Ss     0:00 /x86_64-bottlerocket-linux-gnu/sys-root/usr/sbin/wickedd --systemd --foreground
system_u:system_r:network_t:s0     3280 ?        Ss     0:00 /x86_64-bottlerocket-linux-gnu/sys-root/usr/sbin/wickedd-nanny --systemd --foreground
system_u:system_r:clock_t:s0       3555 ?        Ss     0:00 /usr/sbin/chronyd -d -F -1
system_u:system_r:clock_t:s0       3610 ?        S      0:00 /usr/sbin/chronyd -d -F -1

Files are labeled as expected.

# ls -latrZ /var/lib/wicked
-rwx------. 1 root root system_u:object_r:lease_t:s0   38 Jul  7 17:39 iaid.xml
-rwx------. 1 root root system_u:object_r:lease_t:s0   55 Jul  7 17:39 duid.xml
-rw-------. 1 root root system_u:object_r:lease_t:s0  996 Jul  7 20:03 lease-eth0-dhcp-ipv4.xml

# ls -latrZ /var/lib/chrony/
-rw-r--r--. 1 chrony chrony system_u:object_r:measure_t:s0 1121 Jul  7 20:09 169.254.169.123.dat
-rwx------. 1 chrony chrony system_u:object_r:measure_t:s0   42 Jul  7 20:09 drift

# ls -latrZ /var/lib/systemd/
-rwxr-xr-x.  1 root root system_u:object_r:state_t:s0  512 Jul  8 14:51 random-seed
drwxr-xr-x.  2 root root system_u:object_r:state_t:s0 4096 Jul  8 14:51 coredump
drwxr-xr-x.  2 root root system_u:object_r:state_t:s0 4096 Jul  8 14:51 catalog

# ls -latrZ /var/log/journal/ec274cd5add60d0d045b205a4a4317a8/
-rw-r-----. 1 root systemd-journal system_u:object_r:state_t:s0 8388608 Jul  8 14:58 system.journal

The machine ID is consistent across reboots and stop/start for both m4.xlarge and m5.xlarge.

/* m4.xlarge */
# cat /sys/hypervisor/uuid
ec274cd5-add6-0d0d-045b-205a4a4317a8

# cat /etc/machine-id
ec274cd5add60d0d045b205a4a4317a8

/* m5.xlarge */
# cat /etc/machine-id
ec2e505a672c97f59ba650eb81e9ed6d

# cat /sys/class/dmi/id/product_uuid
ec2e505a-672c-97f5-9ba6-50eb81e9ed6d

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

Before saving clock measurements and DHCP leases to durable storage,
we want to make sure they can't be modified by an untrusted workload.

chronyd and wicked are both network-facing daemons, so we have the
additional goal of limiting their access to the host OS, to mitigate
the impact of a compromise.

dbus-broker does not need to persist any state, but could be exposed
to untrusted local input, and benefits from similar confinement.

systemd also persists some state, such as the journal and the random
seed, so we label that data as well to prevent unexpected changes.

Signed-off-by: Ben Cressey <bcressey@amazon.com>
Now that clock measurements are protected by the SELinux policy, we
can save them on durable storage so they are available after an OS
update.

Signed-off-by: Ben Cressey <bcressey@amazon.com>
Now that lease files are protected by the SELinux policy, we can save
them on durable storage so they are available after an OS update.

Signed-off-by: Ben Cressey <bcressey@amazon.com>
This partially reverts 58b0289. We do not use the systemd feature
for private directories, so this change only affects systemd's own
programs.

Signed-off-by: Ben Cressey <bcressey@amazon.com>
We don't have a good way to persist the machine ID in a place that's
accessible during early boot, so our best bet is to always generate
the same ID.

Both Xen and KVM can provide a UUID to identify guests, and systemd
already uses the KVM value if available. This patch extends the logic
to check for the Xen value as well.

Signed-off-by: Ben Cressey <bcressey@amazon.com>
Signed-off-by: Ben Cressey <bcressey@amazon.com>
@bcressey bcressey changed the title persist state for wicked and chrony persist state for wicked, chrony, and systemd Jul 8, 2020
@bcressey bcressey linked an issue Jul 8, 2020 that may be closed by this pull request
2 tasks
@bcressey bcressey requested a review from tjkirch July 8, 2020 16:17
Copy link
Contributor

@tjkirch tjkirch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was left confused after Jake's comment - we're not losing /var/cache on reboot, right? We rely on it for migrations, at least, and surely other things.

The testing focuses on SELinux, and does show the machine ID, but you confirmed that all these things are persisting over reboot? Old journal entries, same machine ID, chrony timings, wicked lease...

@bcressey
Copy link
Contributor Author

bcressey commented Jul 8, 2020

I was left confused after Jake's comment - we're not losing /var/cache on reboot, right? We rely on it for migrations, at least, and surely other things.

Correct, /var/cache is not going away.

The testing focuses on SELinux, and does show the machine ID, but you confirmed that all these things are persisting over reboot? Old journal entries, same machine ID, chrony timings, wicked lease...

Yes, I've confirmed that the files are persisted across reboot.

@bcressey
Copy link
Contributor Author

bcressey commented Jul 8, 2020

I've also tested a downgrade from a system with the stateful files into an older version. wicked and chrony were both stateless before and didn't expect files in /var/lib, so those were fine.

My concern was with journald, which previously defaulted to Storage=auto, which uses a persistent journal if /var/log/journal exists, and otherwise uses /run/log/journal. Since the persistent journal is created by the upgrade, it will still be there on the downgrade, and labeled with an SELinux label that didn't exist in the older policy.

It ended up working fine, though, since the policy allows for writes to files with no label or an unknown label.

Copy link
Contributor

@jamieand jamieand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bcressey bcressey merged commit 556ae73 into bottlerocket-os:develop Jul 9, 2020
@bcressey bcressey deleted the persist-state branch July 9, 2020 21:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants