Bug 1020241 - rpm verify of nss-sysinit fails
Summary: rpm verify of nss-sysinit fails
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: nss
Version: 6.5
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: nss-nspr-maint
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 10:47 UTC by Hubert Kario
Modified: 2017-09-06 12:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-06 12:56:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 990631 0 urgent CLOSED file permissions of pkcs11.txt/secmod.db must be kept when modified by NSS 2021-02-22 00:41:40 UTC

Internal Links: 990631

Description Hubert Kario 2013-10-17 10:47:31 UTC 
Description of problem:
After installing nss together with p11-kit-trust and ca-certificates, the rpm -V fails.

Version-Release number of selected component (if applicable):
p11-kit-trust-0.18.5-2.el6.x86_64
nss-sysinit-3.15.1-15.el6.x86_64
ca-certificates-2013.1.94-65.0.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. Install above mentioned packages
2. rpm -V nss-sysinit

alternatively:
1. chmod 644 /etc/pki/nssdb/pkcs11.txt
1. rpm -V nss-sysinit

Actual results:
 .M....... c /etc/pki/nssdb/pkcs11.txt

Expected results:
no output

Additional info:
Comment 1 Elio Maldonado Batiz 2014-02-14 15:19:32 UTC 
I cannot reproduce this problem with nss-sysinit-3.15.3

# ls -l /etc/pki/nssdb/pkcs11.txt 
-rw-r--r--. 1 root root 451 Jan 21 19:33 /etc/pki/nssdb/pkcs11.txt

# rpm -q nss-sysinit p11-kit-trust ca-certificates
nss-sysinit-3.15.3-6.el6_5.x86_64
p11-kit-trust-0.18.5-2.el6_5.2.x86_64
ca-certificates-2013.1.95-65.1.el6_5.noarch
# rpm -V nss-sysinit

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