Bug 3996

Summary: rpm --rebuilddb creates files with current umask
Product: [Retired] Red Hat Linux Reporter: v.kuhlmann
Component: rpmAssignee: Jeff Johnson <jbj>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 6.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-08-16 19:09:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description v.kuhlmann 1999-07-12 06:40:01 UTC
I just installed the updated rpm-3.0.2-6.0, and did a
--rebuilddb (although strictly not necessary). It turns out
that the files under /var/lib/rpm are recreated with the
current umask of root, i.e. 600. (I anyway run root with
umask 077)

This should not be the case. THese files should always get

Comment 1 Jay Turner 1999-07-12 14:56:59 UTC
Indeed the files in /var/lib/rpm get written with root's umask, so in
the case of a 077 umask, all of the files are getting written RW for
root only.  Not sure whether this is a problem or not, but have
forwarded it to a developer for further action.

Comment 2 Jeff Johnson 1999-08-16 19:09:59 UTC
Unset umask before rebuilding the database. There's no way that
rpm can identify that /var/lib/rpm/* should be mode 0644 or mode 0600.