Bug 950155

Summary: missing partial RELRO [6.5]
Product: Red Hat Enterprise Linux 6 Reporter: Aleš Mareček <amarecek>
Component: nss-softoknAssignee: Elio Maldonado Batiz <emaldona>
Status: CLOSED ERRATA QA Contact: Alicja Kario <hkario>
Severity: high Docs Contact:
Priority: high    
Version: 6.4CC: hkario, jkurik, ksrot, sforsber, thoger
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nss-softokn-3.14.3-4.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 950152 Environment:
Last Closed: 2013-11-21 06:13:24 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:
Bug Depends On: 950152    
Bug Blocks: 985955    

Description Aleš Mareček 2013-04-09 18:35:31 UTC
+++ This bug was initially created as a clone of Bug #950152 +++

Description of problem:
Partial RELRO is missing in the new build of nss-softokn

Version-Release number of selected component (if applicable):
nss-softokn-3.14.3-1.el6_4

How reproducible:
Always

Steps to Reproduce:
1. Run test: /CoreOS/nss/Sanity/partial-RELRO-support-for-nss-nspr-nss-softokn-nss-util
  
Actual results:
FAIL

Expected results:
PASS

Additional info:
/usr/lib64/libnssdbm3.so FAIL
/usr/lib64/libsoftokn3.so FAIL
/usr/lib64/nss/unsupported-tools/bltest PASS
/usr/lib64/nss/unsupported-tools/fipstest PASS
/usr/lib64/nss/unsupported-tools/shlibsign PASS
/usr/lib/libnssdbm3.so FAIL
/usr/lib/libsoftokn3.so FAIL
/usr/lib/nss/unsupported-tools/bltest PASS
/usr/lib/nss/unsupported-tools/fipstest PASS
/usr/lib/nss/unsupported-tools/shlibsign PASS
:: [   FAIL   ] :: Testing package: nss-softokn (Expected 0, got 1)

Comment 4 Suzanne Forsberg 2013-07-18 12:37:26 UTC
*** Bug 950152 has been marked as a duplicate of this bug. ***

Comment 13 errata-xmlrpc 2013-11-21 06:13:24 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.

http://rhn.redhat.com/errata/RHBA-2013-1558.html