Bug 1294301 - SELinux local (new) customisations lost after selinux-policy-targeted update
SELinux local (new) customisations lost after selinux-policy-targeted update
Status: CLOSED DUPLICATE of bug 1291601
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
x86_64 Linux
high Severity high
: ---
: ---
Assigned To: Miroslav Grepl
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-12-26 12:19 EST by Tibbs Brookside
Modified: 2016-01-04 08:48 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-01-04 08:48:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tibbs Brookside 2015-12-26 12:19:55 EST
Description of problem:
SELinux context entries for local (new) files and directories are lost following updates to the selinux-policy-targeted package.

For example, if I add a new entry as follows:

semanage fcontext -a -t httpd_sys_content_t "/data/www(/.*)?"
restorecon -R -v /data/www/

As far as I understand, these local (new) customisations get stored in:

but this file gets replaced when the selinux-policy-targeted package is updated, and so all my customisations get lost:

rpm -qf /etc/selinux/targeted/contexts/files/file_contexts.local

Should the package replace this file, or reinstate the contents as part of the update (as appears to be done for the /etc/selinux/targeted/contexts/files/file_contexts file)?

Version-Release number of selected component (if applicable):
Comment 1 Lukas Vrabec 2016-01-04 08:48:03 EST
This should work *from* selinux-policy-targeted-3.13.1-158.fc23.noarch to selinux-policy-targeted-3.13.1-159.fc23.noarch and higher package update.

*** This bug has been marked as a duplicate of bug 1291601 ***

Note You need to log in before you can comment on or make changes to this bug.