Bug 1700920

Summary:	Remove capabilities instead of setting empty caps via. --setcaps and --restore
Product:	Red Hat Enterprise Linux 8	Reporter:	Ryan Blakley <rblakley>
Component:	rpm	Assignee:	Pavlina Moravcova Varekova <pmoravco>
Status:	CLOSED ERRATA	QA Contact:	Eva Mrakova <emrakova>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0	CC:	dmach, emrakova, ffesti, pmoravco, ryangbowen
Target Milestone:	rc	Keywords:	Triaged
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rpm-4.14.2-23.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:22:37 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 Ryan Blakley 2019-04-17 16:16:18 UTC

Description of problem: When running --setcaps or --restore, all capabilities are getting set to empty capabilities if the file doesn't have any capabilities defined, instead of removing the capabilities. This causes the files/directories to light up with red backgrounds when running ls. Below is the upstream commit to fix the issue.


Steps to Reproduce:
root@ryan-rhel8 ~ # rpm --setcaps util-linux
root@ryan-rhel8 ~ # getcap /var/log/lastlog 
/var/log/lastlog =                          <<--empty capability
root@ryan-rhel8 ~ # cp rpmpopt-4.14.2 /usr/lib/rpm/
cp: overwrite '/usr/lib/rpm/rpmpopt-4.14.2'? y
root@ryan-rhel8 ~ # rpm --setcaps util-linux
root@ryan-rhel8 ~ # getcap /var/log/lastlog 
root@ryan-rhel8 ~ #


Additional info:
https://github.com/rpm-software-management/rpm/commit/b4178c979fff344a1c5142a305f274dd9aff8f45

Comment 8 errata-xmlrpc 2019-11-05 22:22:37 UTC

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.

https://access.redhat.com/errata/RHBA-2019:3584

Comment 9 Panu Matilainen 2019-12-03 15:36:37 UTC

*** Bug 1778361 has been marked as a duplicate of this bug. ***