Ubuntu Noble warden-specific systemd hardening#506
Ubuntu Noble warden-specific systemd hardening#506mike-jc wants to merge 6 commits intocloudfoundry:ubuntu-noblefrom
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
4a9c207 to
7cd21d2
Compare
|
Given that we use our containerized stemcells for a lot of testing, I'd be inclined to have it mimic production as much as conveniently possible. I'd prefer to see this an explicit list of services to disable in a container instead of an allow list of services. We recently did some of this in #486 (noble) and #500 (jammy). |
d16d45f to
0319bcc
Compare
Thank you @mkocher, that's a good point. I removed the allowlisting of systemd services and tested the mask list approach. The {{systemd-binfmt}} service is already masked, and testing confirms this is sufficient for warden/boshlite on both Jammy and Noble: during testing with the latest official Noble stemcell and the Jammy stemcell built on PR 500, along with a dev release containing PR 60 for Docker CPI, all HAProxy acceptance tests passed successfully. So I close this PR and the PR for Jammy. We need only Docker CPI changes to have stemcells work there. |
This is for Ubuntu Noble stemcell.
These changes are related to issues:
Added a new stage
base_systemd_cleanto thewarden_stagescollection, which is applied during stemcell build, and removes all custom and optional systemd services, keeping only the necessary minimum set.