Bug 436652

Summary:	wrong selinux label on rpcbind
Product:	[Fedora] Fedora	Reporter:	Dave Jones <davej>
Component:	rpcbind	Assignee:	Steve Dickson <steved>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	dwalsh, pfrields
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-03-18 21:36:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dave Jones 2008-03-08 20:17:37 UTC

After a yum update, my nfs server stopped working.
I tracked this down to /var/lib/rpcbind/ containing mislabelled files.

(15:14:46:root@gelk:lib)# ll rpcbind/ -Z
-rw-------  rpc root system_u:object_r:var_lib_t      portmap.file
-rw-------  rpc root system_u:object_r:var_lib_t      rpcbind.file
(15:14:48:root@gelk:lib)# restorecon rpcbind/*
(15:14:58:root@gelk:lib)# ll rpcbind/ -Z
-rw-------  rpc root system_u:object_r:rpcbind_var_lib_t portmap.file
-rw-------  rpc root system_u:object_r:rpcbind_var_lib_t rpcbind.file

I'm not sure if this a problem with the policy or rpcbind doing something wrong.

Comment 1 Daniel Walsh 2008-03-10 14:13:21 UTC

How was the /var/lib/rpcbind directory created?  If it is part of the package as
it is in Rawhide, then it would be labeled correctly.    Did you remove the
directory?

Comment 2 Steve Dickson 2008-03-15 11:54:10 UTC

This rpcbind spec file creates /var/lib/rpcbind when the package is
installed and removed when the packages is erased.

Comment 3 Daniel Walsh 2008-03-17 13:30:21 UTC

RIght this would label the directory correctly.  So I surmise that someone or
some package removed the directory and recreated it, causing the directory to
get the file context of it's parent.

Comment 4 Dave Jones 2008-03-18 21:36:39 UTC

not guilty!

I've no idea what caused it to lose its label. This box has run f8 the whole
time, and hasn't been booted with selinux=0 at all.

seems to be labelled correctly after removing/reinstalling the package anyway.

spooky.