Bug 130421 - should run "restorecon $FONT_UNIX_DIR" for SE Linux
Summary: should run "restorecon $FONT_UNIX_DIR" for SE Linux
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11   
(Show other bugs)
Version: rawhide
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
: 130969 (view as bug list)
Depends On:
Blocks: FC3Blocker FC3SELinux
TreeView+ depends on / blocked
 
Reported: 2004-08-20 12:54 UTC by Russell Coker
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-15 06:49:43 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Russell Coker 2004-08-20 12:54:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)

Description of problem:
After creating $FONT_UNIX_DIR the start script should run:
text -s /sbin/restorecon && /sbin/restorecon $FONT_UNIX_DIR

This will set the SE Linux context of the new directory to the correct type.

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


How reproducible:
Always

Steps to Reproduce:
Boot SE Linux and run "ls -ldZ /tmp/.font-unix", observe that the context is system_u:object_r:initrc_tmp_t not system_u:object_r:xfs_tmp_t .

Additional info:

Comment 1 Mike A. Harris 2004-09-15 06:49:43 UTC
Added to 6.8.0-5 in CVS, will appear in rawhide after FC3t2.

Comment 2 Mike A. Harris 2004-09-15 21:59:21 UTC
*** Bug 130969 has been marked as a duplicate of this bug. ***

Comment 3 Mike A. Harris 2004-09-15 22:02:41 UTC
I've updated the fix for this to move the call to restorecon down
after the chmod/chown as the patch in bug 130969 does, in case
chmod/chown cause problems after restorecon, just to be safe.

This new fix will be in 6.8.0-6


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