RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1429775 - NSS_LIBDIR not propagated to ../security/nss.cfg
Summary: NSS_LIBDIR not propagated to ../security/nss.cfg
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: java-1.8.0-openjdk
Version: 6.10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Andrew John Hughes
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1503147
TreeView+ depends on / blocked
 
Reported: 2017-03-07 04:24 UTC by Andrew John Hughes
Modified: 2017-12-06 12:07 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1417424
Environment:
Last Closed: 2017-12-06 12:07:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Andrew John Hughes 2017-03-07 04:24:06 UTC 
There is a broken nss.cfg file in the java-1.8.0-openjdk installation. We should either fix or remove it. 

The Fedora report of this issue is below:

+++ This bug was initially created as a clone of Bug #1417424 +++

Description of problem:

In /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.111-5.b16.fc25.x86_64/jre/lib/security/nss.cfg, I see this:
...
nssLibraryDirectory = @NSS_LIBDIR@
...

In java-1.8.0-openjdk.spec, I see this:
%global NSS_LIBDIR %(pkg-config --variable=libdir nss)


I read this, as @NSS_LIBDIR@ in nss.cfg is supposed to be replaced with
/usr/lib64 (rsp. /usr/lib), i.e. a packaging bug. 


Version-Release number of selected component (if applicable):
java-1.8.0-openjdk-headless-1.8.0.111-5.b16.fc25.x86_64

Additional info:
I don't have the faintest clue about the consequences and seriousness of this bug.

--- Additional comment from Severin Gehwolf on 2017-01-30 04:29:43 EST ---

Same issue with latest stable packages:

$ grep NSS_LIBDIR /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-1.b14.fc24.x86_64/jre/lib/security/nss.cfg
nssLibraryDirectory = @NSS_LIBDIR@
$ rpm -q java-1.8.0-openjdk
java-1.8.0-openjdk-1.8.0.121-1.b14.fc24.x86_64

--- Additional comment from Severin Gehwolf on 2017-01-30 05:26:44 EST ---

Andrew, is this config file needed at all?

--- Additional comment from jiri vanek on 2017-01-30 08:39:52 EST ---

There used to be :

# Install nss.cfg right away as we will be using the JRE above
cp -a %{SOURCE8} $JAVA_HOME/jre/lib/security/
sed -i -e s:@NSS_LIBDIR@:%{NSS_LIBDIR}:g $JAVA_HOME/jre/lib/security/nss.cfg

Its somehow no longer there.

--- Additional comment from jiri vanek on 2017-01-30 08:41:09 EST ---

s/SOURCE8/SOURCE11 for current version

--- Additional comment from Andrew John Hughes on 2017-03-06 23:18:21 EST ---

(In reply to jiri vanek from comment #3)
> There used to be :
> 
> # Install nss.cfg right away as we will be using the JRE above
> cp -a %{SOURCE8} $JAVA_HOME/jre/lib/security/
> sed -i -e s:@NSS_LIBDIR@:%{NSS_LIBDIR}:g $JAVA_HOME/jre/lib/security/nss.cfg
> 
> Its somehow no longer there.

It seems it never made it to java-1.8.0-openjdk at all. The config file was added, but not the substitution nor the addition of the PKCS11 provider to java.security.
It's broken in RHEL's java-1.8.0-openjdk too. java-1.6.0-openjdk is also broken, but in a different way. java-1.7.0-openjdk is the only version that seems to have this correct.

nss.cfg is a configuration file for the PKCS11 provider. It's called by the addition of a line to java.security:

#security.provider.10=sun.security.pkcs11.SunPKCS11 ${java.home}/lib/security/nss.cfg

However, that's not present in java-1.8.0-openjdk so the file never gets read and thus the invalid contents are never used.

As it's been broken for the entire lifetime of java-1.8.0-openjdk, I suggest just deleting it.

Assigning to Jiri so he can decide whether to delete or fix it in Fedora.
Comment 4 Jan Kurik 2017-12-06 12:07:05 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.