Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
When using the "-Z/--context" option in the cp utility, the SELinux context of a file was not changed if the file destination already existed. The utility has been modified and the context is changed as expected. However, this option is not portable to other systems.
Description of problem:
cp -Z , security context of file is NOT changed
Version-Release number of selected component (if applicable):
coreutils-8.4-13.el6.ppc64
it could see the same on rhel5u7
How reproducible:
deterministic
Steps to Reproduce:
# ORIG_CONTEXT=root:object_r:file_t
# NEW_CONTEXT=root:object_r:tmp_t
# rm -f file-a file-b
# touch file-a
# ls -Z file-a
-rw-r--r--. root root unconfined_u:object_r:tmp_t:s0 file-a
# cp -Z $ORIG_CONTEXT file-a file-b
# ls -Z file-b
-rw-r--r--. root root root:object_r:file_t file-b
# cp -Z $NEW_CONTEXT file-a file-b
cp: overwrite `file-b'? y
# ls -Z file-b
-rw-r--r--. root root root:object_r:file_t file-b
Actual results:
context of file-b is NOT changed
Expected results:
context is file-b is changed
Additional info:
man page says
-Z, --context=CONTEXT
set security context of copy to CONTEXT
I am observing the same behavior on F-14 coreutils. The problem is that cp -Z uses setfscreatecon(), which affects only newly created files. As a workaround you can use cp --remove-destination -Z ...
Comment 3RHEL Program Management
2011-07-05 23:56:52 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
When using the "-Z/--context" option in the cp utility, the SELinux context of a file was not changed if the file destination already existed. The utility has been modified and the context is changed as expected. However, this option is not portable to other systems.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1693.html
Description of problem: cp -Z , security context of file is NOT changed Version-Release number of selected component (if applicable): coreutils-8.4-13.el6.ppc64 it could see the same on rhel5u7 How reproducible: deterministic Steps to Reproduce: # ORIG_CONTEXT=root:object_r:file_t # NEW_CONTEXT=root:object_r:tmp_t # rm -f file-a file-b # touch file-a # ls -Z file-a -rw-r--r--. root root unconfined_u:object_r:tmp_t:s0 file-a # cp -Z $ORIG_CONTEXT file-a file-b # ls -Z file-b -rw-r--r--. root root root:object_r:file_t file-b # cp -Z $NEW_CONTEXT file-a file-b cp: overwrite `file-b'? y # ls -Z file-b -rw-r--r--. root root root:object_r:file_t file-b Actual results: context of file-b is NOT changed Expected results: context is file-b is changed Additional info: man page says -Z, --context=CONTEXT set security context of copy to CONTEXT