466118 - Need a negative test case for NSS_Init in an empty DB directory

Status: NEW

(NSS :: Test, enhancement, P2)

Description

[Nelson Bolyard (seldom reads bugmail)]

NSS has several initialization functions.  Among them are:
- NSS_InitReadWrite() which tells the token to open the DBs for reading and 
    writing and to create them if necessary (when they don't exist), and
- NSS_Init() which tells the token to open the DBs read-only, and to FAIL 
    if the DBs don't exist or cannot be opened.

It seems that NSS test scripts have no test to ensure that NSS_Init fails
when no DBs exist in the named directory.  And as it turns out, in shared DB
mode, NSS_Init behaves like NSS_InitReadWrite. :(

So, we need a negative test case, that 
1) creates an empty directory and then 
2) attempts to initialize NSS with NSS_Init using that directory, and 
3) checks to see if NSS reports success or failure, and 
4) checks to see if NSS creates any DB files or not.  

If NSS is working correctly, it should report failure and not create any 
DB files in that directory.

This test should be done for both shared DB and regular (for sql and dbm),
and should produce the correct result in both cases.  

One easy way to call NSS_Init on a given directory is to use the command
  certutil -L -d DBDIR
Since this command only needs to read the token contents, it uses NSS_Init
to open the DBs read-only.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee is inactive on Bugzilla, and this bug has priority 'P2'.
:beurdouche, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 2

[Marco Castelluccio [:marco]]

We have modified the bot to only consider P1 as high priority, so I'm cancelling the needinfo here.