A link /libnss3.so is created when installing the package or when updating the jks-keystore

Bug #1065877 reported by Björn Torkelsson
38
This bug affects 9 people
Affects Status Importance Assigned to Milestone
ca-certificates-java (Debian)
Fix Released
Unknown
ca-certificates-java (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When installing ca-certificates-java or when updating the jks-keystore with update-ca-certificates (which calls the jks-keystore hook) a link /libnss3.so is created, pointing to /usr/lib/x86_64-linux-gnu/libnss3.so.

It is fixed in a later version of ca-certificates-java but it would great to have this fixed in the version available in 12.04 too as it is a LTS release.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ca-certificates-java 20110912ubuntu6
ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30
Uname: Linux 3.2.0-32-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Fri Oct 12 10:12:52 2012
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US
 SHELL=/bin/bash
SourcePackage: ca-certificates-java
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Björn Torkelsson (torkel) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ca-certificates-java (Ubuntu):
status: New → Confirmed
Revision history for this message
Marcus Habermehl (bmh1980de) wrote :

I have the same link in 12.10 with i386 arch. There seems no line with 'nssLibraryDirectory' in /etc/$jvm/security/nss.cfg. This line is used in postinst to determine the destination path for the symlink.

Revision history for this message
Simon Déziel (sdeziel) wrote :

Extract of the changelog:

ca-certificates-java (20120524) unstable; urgency=low

  [ Marc Deslauriers ]
  [...]
  * debian/postinst: don't put a symlink in / if jvm doesn't contain nss
    configuration. (Closes: #665754, #665749).

This means that Trusty and later are not affected.

Changed in ca-certificates-java (Ubuntu):
status: Confirmed → Fix Released
Changed in ca-certificates-java (Debian):
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.