Bug 828097

Summary:	security-policy-targeted rpm postinst script traverses mounted media
Product:	[Fedora] Fedora	Reporter:	Malcolm Tredinnick <malcolm.tredinnick>
Component:	selinux-policy-targeted	Assignee:	Miroslav Grepl <mgrepl>
Status:	CLOSED ERRATA	QA Contact:	Ben Levenson <benl>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	dwalsh
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-17 00:05:21 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 Malcolm Tredinnick 2012-06-04 08:50:36 UTC

Description of problem:

After an upgrade to security-policy-targeted via yum today, the postinst script did it's standard restorecon invocation. At the time, I had a 1 TB USB hard-drive mounted. Fedora 17 has moved the mount point to /var/run/media/...., rather than the former /media location. Sadly, /var/run is one of the directories that restorecon tries to relabel. A few hours later, it finally finished.


Version-Release number of selected component (if applicable):

It was upgrading to selinux-policy-targeted-3.10.0-128.fc17.


How reproducible:

Should be always reproducible. The particular restorecon invocation, according to ps was

/sbin/restorecon -R /root /var/log /var/run /etc/passwd /etc/passwd- /etc/passwdqc.conf /etc/group /etc/group-


Steps to Reproduce:
1. Mount external (readwritable) device as any user.
2. Upgrade selinux-policy-targeted
  
Actual results:

Much waiting and disk activity. Unhappiness.


Expected results:

It seems like the intention is that random data directories should be skipped in this process. /media wasn't in the F16 restorecon list for this scriptlet and /home never is. So I would expect /var/run/media to be excluded in the F17 world.

Comment 1 Miroslav Grepl 2012-06-04 09:44:33 UTC

Fixed in selinux-policy-3.10.0-129.fc17

Comment 2 Fedora Update System 2012-06-11 21:03:34 UTC

selinux-policy-3.10.0-130.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-130.fc17

Comment 3 Fedora Update System 2012-06-16 00:00:27 UTC

Package selinux-policy-3.10.0-130.fc17:
* should fix your issue,
* was pushed to the Fedora 17 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.10.0-130.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-9520/selinux-policy-3.10.0-130.fc17
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-06-17 00:05:21 UTC

selinux-policy-3.10.0-130.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.