Bug 1182307 - incorrect specification of ghost file mlocate.db in mlocate package
Summary: incorrect specification of ghost file mlocate.db in mlocate package
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mlocate
Version: 5.11
Hardware: All
OS: All
unspecified
low
Target Milestone: rc
: ---
Assignee: Michal Sekletar
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On: 1182304 1182306 1185798
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-14 20:23 UTC by Paulo Andrade
Modified: 2015-07-10 08:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-10 08:11:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Paulo Andrade 2015-01-14 20:23:50 UTC
The mlocate rpm correctly defines mlocate.db to be a ghost file. However it is incorrectly stated that this file is owned by group root and that the mode is 644. When updatedb runs it creates the files with group slocate and mode 640.
This leads to rpm verification errors, which lead to failed compliance checks.

This bug may be present in other RHEL versions as well.

A simple mlocate.spec pseudo patch would be:

-%ghost %{_localstatedir}/lib/mlocate/mlocate.db
+%ghost %attr(0640,root,slocate) %{_localstatedir}/lib/mlocate/mlocate.db

Comment 1 RHEL Program Management 2015-01-15 08:47:58 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 unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 2 Michal Sekletar 2015-07-10 08:11:30 UTC
Fixing this trivial/cosmetic issue via z-stream would be just waste of everyone's time.


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