506140 - SECMOD_OpenUserDB malfunctions after a SECMOD_CloseUserDB call.

Status: RESOLVED DUPLICATE of bug 588269

(NSS :: Libraries, defect)

Description

[Wan-Teh Chang]

Chromium has two unit tests that require NSS to open an
additional NSS database (in the old DBM format) as "user db".

We found that if we run these two unit tests in a row (in
the same process), the second unit test fails, but if we run
these two unit tests separately (in two processes), they
pass.

The failure of the second unit test seems to be caused by
our SECMOD_CloseUserDB call at the end of the first unit
test.  If we remove our SECMOD_CloseUserDB call, we can
run both unit tests in a row.

Bob, do you know what's wrong?

Comment 1

[Robert Relyea]

Not off the top of my head, do you have a simple test case?

Last time I used the call I could open and close the databases without problem.

bob

Comment 2

[Wan-Teh Chang]

I will try to write a simple test case when I have time.  Our code
opens an additional NSS database and then uses that slot to do
SDK decryption.  We had to duplicate most of the code in PK11SDR_Decrypt
because that function is hardcoded to use the internal key slot.

We found that things also go wrong if we open, close, and then
re-open the same user db.  The two user dbs don't need to be
different.