Bug 1294301 - SELinux local (new) customisations lost after selinux-policy-targeted update
Summary: SELinux local (new) customisations lost after selinux-policy-targeted update
Keywords:
Status: CLOSED DUPLICATE of bug 1291601
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 23
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-26 17:19 UTC by Tibbs Brookside
Modified: 2016-01-04 13:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-04 13:48:03 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tibbs Brookside 2015-12-26 17:19:55 UTC
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:
/etc/selinux/targeted/contexts/files/file_contexts.local

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
selinux-policy-targeted-3.13.1-158.fc23.noarch

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):
selinux-policy-targeted-3.13.1-158.fc23.noarch

Comment 1 Lukas Vrabec 2016-01-04 13:48:03 UTC
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.