133646 - NSS_shutdown failure

Status: RESOLVED DUPLICATE of bug 133584

(NSS :: Libraries, defect)

Description

[Neil Brittliff]

In previous releases of NSS it was possible to connect from one directory to 
another simply by performing:

NSS_InitReadWrite("d:\\nss\\store1");

PK11_Logout(PK11_GetInternalKeySlot());
NSS_Shutdown();

NSS_InitReadWrite("d:\\nss\\store2");

NSS still remembers the old store - d:\\nss\\store1 in 3.4.  

All the utility programs e.g. certutil will not show this up since operate on 
the one directory.

Comment 1

[Wan-Teh Chang]

Assigned the bug to Bob.

This bug looks like a duplicate of bug 133584.

Comment 2

[Wan-Teh Chang]

Please try replacing
    PK11_Logout(PK11_GetInternalKeySlot());
with
    PK11SlotInfo *slot;

    slot = PK11_GetInternalKeySlot();
    PK11_Logout(slot);
    PK11_FreeSlot(slot);

This is because slots are reference counted.
PK11_GetInternalKeySlot() increments the reference
count of the slot, so you need to call PK11_FreeSlot()
to decrement the reference count when you are done
with the slot reference.

In NSS 3.3.x, the DB is separate from the NSS internal
module and is always closed in NSS_Shutdown.  In NSS
3.4, the DB is part of the NSS internal module, and
won't be closed if there is a leaked slot reference.

Comment 3

[Neil Brittliff]

I tried that piece of code - unfortunately, it still doesn't seem to work 

    PK11SlotInfo *slot;

    slot = PK11_GetInternalKeySlot();
    PK11_Logout(slot);
    PK11_FreeSlot(slot);

You can't switch to another directory after initialisation which you could in 
in NSS 3.1.1, etc

Comment 4

[Wan-Teh Chang]

Changed the QA contact to Bishakha.

Comment 5

[Robert Relyea]

*** This bug has been marked as a duplicate of 133584 ***