-
Notifications
You must be signed in to change notification settings - Fork 18
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
Get CLIP RHEL7 Booting in Enforcing #86
Comments
…y CLIP - These were removed when pulling in a new refpolicy (#699d65b) - Remove unneeded files - Secstate is no longer needed, so it may be removed
…sing shadow Fixed in 2fef7c5
Rather than cherry-pick commits, we have updated the base refpolicy to pebenito/refpolicy@5fd2953 Further development is being done on top of this to get CLIP booting in Enforcing. |
- Pull in @csmith-tresys's additional interfaces and policy
- Various Makefile/specfile changes
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Give systemd-utmp can_relabelto_binary_policy to clear up constraints
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Give systemd-utmp can_relabelto_binary_policy to clear up constraints
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Give systemd-utmp can_relabelto_binary_policy to clear up constraints
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Give systemd-utmp can_relabelto_binary_policy to clear up constraints
- Many /sbin/ file contexts do not have their corresponding /usr/sbin files labeled properly. Label them en mass and sort contexts appropriately.
- Many /sbin/ file contexts do not have their corresponding /usr/sbin files labeled properly. Label them en mass and sort contexts appropriately.
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Give systemd-utmp can_relabelto_binary_policy to clear up constraints
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Add some file_contexts.subs_dist mappings - Label some unlabeled files
…olicy - Get rid of conditional and remove redundant policy.
- Various Makefile/specfile changes
… scripts Systemd still supports traditional init scripts, so modify init_daemon_domain and init_system_domain to allow both initrc_t and init_t transitions if systemd policy is turned on. Else, default to only intrc_t transitions.
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Add some file_contexts.subs_dist mappings - Label some unlabeled files - Make semanage_t an init_system_domain, so initrc_t can transition to semanage and run genhomedircon. - Begin labeling unit files
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Add some file_contexts.subs_dist mappings - Label some unlabeled files - Make semanage_t an init_system_domain, so initrc_t can transition to semanage and run genhomedircon. - Begin labeling unit files
- Various Makefile/specfile changes
… scripts Systemd still supports traditional init scripts, so modify init_daemon_domain and init_system_domain to allow both initrc_t and init_t transitions if systemd policy is turned on. Else, default to only intrc_t transitions.
- Pull in @csmith-tresys's additional interfaces and policy - Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Add some file_contexts.subs_dist mappings - Label some unlabeled files - Make semanage_t an init_system_domain, so initrc_t can transition to semanage and run genhomedircon. - Begin labeling unit files
- Separate systemd-service forks into their own contexts - Use existing policy for the following: contrib/readahead (systemd-readahead) contrib/shutdown (systemd-shutdown) system/fstools (systemd-fsck) system/hostname (systemd-hostname) system/logging (systemd-journald) - Add some file_contexts.subs_dist mappings - Label some unlabeled files - Make semanage_t an init_system_domain, so initrc_t can transition to semanage and run genhomedircon. - Begin labeling unit files
@mpalmi please assign a time estimate label for this issue. |
We are currently able to boot in Enforcing, using several permissive domains. |
- Various Makefile/specfile changes
… scripts Systemd still supports traditional init scripts, so modify init_daemon_domain and init_system_domain to allow both initrc_t and init_t transitions if systemd policy is turned on. Else, default to only intrc_t transitions.
- Separate long-running processes/daemons into their own contexts - Let short-running processes fall through to initrc - Label unit files - Add some file_contexts.subs_dist mappings
Fix formatting of systemd interfaces
Add permissions for systemd. Mostly systemd_logind_t
Add permissions for shutdown_t and sshd_keygen_t
The /lib/systemd/rhel-autorelabel problem is related to issue #127. I expect the contexts that aren't valid are from rhel targeted policy and not in the clip policy. |
Issue #86 - Include RHEL_7-Alpha3 policy doc in README.md
- Include systemd policy via init_systemd ifdef - Various Makefile/specfile changes - Modify init interfaces to support old init scripts -- Systemd still supports traditional init scripts, so modify init_daemon_domain and init_system_domain to allow both initrc_t and init_t transitions if systemd policy is turned on. Else, default to only intrc_t transitions. - Separate long-running processes/daemons into their own contexts - Let short-running processes fall through to initrc - Label unit files - Add some file_contexts.subs_dist mappings - Updates for systemd_logind_t - Add permissions for systemd_logind_t
- Include systemd policy via init_systemd ifdef - Various Makefile/specfile changes - Modify init interfaces to support old init scripts -- Systemd still supports traditional init scripts, so modify init_daemon_domain and init_system_domain to allow both initrc_t and init_t transitions if systemd policy is turned on. Else, default to only intrc_t transitions. - Separate long-running processes/daemons into their own contexts - Let short-running processes fall through to initrc - Label unit files - Add some file_contexts.subs_dist mappings - Updates for systemd_logind_t - Add permissions for systemd_logind_t
Closing the master ticket for now, even though all subtickets are not completely resolved. Will open future tickets to fix issues found in testing. |
The first step in addressing #4 is to get CLIP booting in Enforcing.
With the new systemd architecture, there are some significant changes to the way processes spawn.
We will need to pull in Chris PeBenito's changes to the RHEL7 updates to refpolicy (https://github.com/pebenito/refpolicy), specifically the following commits:
add service class to security classes, update various init module interfaces with ifdefs for init_systemd
init_systemd
From there, it is a matter of typical policy development. Gather denials, write policy, wash, rinse, repeat.
As of 4/22, we are able to boot in Enforcing with several permissive domains:
tomhurd/clip@646f163
tomhurd/clip@498ddcd
We really only need a subset of these to be permissive, however:
The future efforts will be driven by pulling all domains out of permissive, but for the sake of getting CLIP booting in Enforcing, the following are the priority:
To get CLIP cleanly booting in Enforcing, the following will need to be done as well:
Some nice-to-haves (not necessarily needed to get CLIP booting in Enforcing):
The text was updated successfully, but these errors were encountered: