Bug 1115212

Summary:	Continuation of OSTree labeling
Product:	[Fedora] Fedora	Reporter:	Colin Walters <walters>
Component:	selinux-policy	Assignee:	Miroslav Grepl <mgrepl>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	dominick.grift, dwalsh, lvrabec, mgrepl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	selinux-policy-3.13.1-116.fc22	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-10 02:59:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Colin Walters 2014-07-01 22:39:48 UTC

This is a followup to bug 1062974.

The following toplevel symlinks the OSTree compose process are labeled default_t:

lrwxrwxrwx. root root system_u:object_r:default_t:s0   media -> run/media
lrwxrwxrwx. root root system_u:object_r:default_t:s0   mnt -> var/mnt
lrwxrwxrwx. root root system_u:object_r:default_t:s0   ostree -> sysroot/ostree

Now for each of these, we need to consider both the symlink itself, as well as its target.  For the symlinks, I see no issue with just labeling them usr_t.  They're immutable content effectively.

The *targets* of the symlinks should match that of the current policy.  For example,

/run/media and /var/mnt should be media_t.  

The last special case is sysroot/ostree - we could discuss adding new labeling for the system OSTree repository, but let's leave that as a separate bug.  Right now it's default_t and that's OK.

Comment 1 Miroslav Grepl 2014-07-02 07:10:46 UTC

Well we label /run/media as mnt_t and /var/mnt as var_t by default. We need to add labeling for these toplevel symlinks.

Comment 2 Jaroslav Reznik 2015-03-03 17:14:52 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 3 Fedora Update System 2015-03-06 22:09:11 UTC

selinux-policy-3.13.1-116.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/selinux-policy-3.13.1-116.fc22

Comment 4 Fedora Update System 2015-03-09 08:38:07 UTC

Package selinux-policy-3.13.1-116.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.13.1-116.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-3508/selinux-policy-3.13.1-116.fc22
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2015-03-10 02:59:22 UTC

selinux-policy-3.13.1-116.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.