Bug 178822

Summary: Should mv always preserve selinux contexts (esp. nfs_t)?
Product: [Fedora] Fedora Reporter: Orion Poplawski <orion>
Component: coreutilsAssignee: Tim Waugh <twaugh>
Status: CLOSED DEFERRED QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: dwalsh
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: 2006-01-25 11:49:52 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Orion Poplawski 2006-01-24 12:18:36 EST
Description of problem:
Not really sure what is best here, but figured an open discussion would be good.
 It looks like mv preserves selinux contexts now, which is good for the most
part.  The issue I'm running into is users moving files from an nfs mount (which
has context nfs_t) into their local directories.  These directories are backed
up by amanda, but amanda doesn't not have permission for nfs_t (a good thing by
default), so these files don't get backed up.  I would guess that some kind of
exclusion list in mv would be unmaintainable.  Perhaps the best fix is for the
nfs mounts to show the contexts on the source system?  Will this ever happen?

Other suggestions?
Comment 1 Tim Waugh 2006-01-24 12:41:24 EST
Adding dwalsh to CC.  Dan, what do you think?

Comment 2 Daniel Walsh 2006-01-25 11:46:29 EST
The goal is to eventually get XAttr support into NFS V3/V4.    Which would allow
us to label files over nfs correctly.