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

Ensure a complete relabeling when switching from disabled to permissive or enforcing #149

Closed
vinzent opened this issue Dec 24, 2016 · 0 comments · Fixed by #151
Closed

Comments

@vinzent
Copy link
Contributor

vinzent commented Dec 24, 2016

Affected Puppet, Ruby, OS and module versions/distributions

  • Module version: 0.5.1-rc0

How to reproduce (e.g Puppet code you use)

  • pre-requirements: systems has selinux disabled but selinux packages installed
class { 'selinux':
  mode => 'permissive',
  type   => 'targeted',
}

What are you seeing

selinux configured for enforcing, but no autorelabel trigger file is created

What behaviour did you expect instead

When SELinux is disabled and desired state is permissive or enforcing the module must create the /.autorelabel trigger file

Any additional information you'd like to impart

If a system has selinux disabled and wants to switch to permissive or enforcing mode a complete relabeling of the filesystem is necessary as within disabled mode no filesystem attributes regarding contexts are written, thus leaving it in a inconsitent state.

EmRowlands pushed a commit to EmRowlands/puppet-selinux that referenced this issue Mar 29, 2023
A complete relabeling is required when switching from disabeld to
permissive or enforcing mode, because selinux file attributes
are not written in disabled mode this leaving the files regarding
selinux in an incosistent state.

This resolves voxpupuli#149
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant