Changes

(NoteStep 2: Determine if a merge is even necessary. If a merge is necessary,NSS will set the present implementation has no way slot to pass the source DBprefix to the functiona 'removable slot'. This needs You can use PK11_IsPerm to be correctedtest for this.)

Step 2: Determine if it If the DB slot token is removable, then an update/merge is necessary to authenticate for the source DB.However,This will not be necessary if there is no database password on either the merge operation has already completed,source or if the source DB had no password. To determine thistarget database, the applicationcalls a function to ask if then NSS has already completed the token in the DB slot is removablemerge. '''FIX ME'' Thefunction to be called You can test for that purpose has not yet been made public, sothis withthose details are TBD. That needs to be correctedPK11_NeedLogin(). If the DB slot token PK11_NeedLogin() is removable, true then it is necessary to authenticateto the source token, at step 3 below. If the token is not removable,then it NOT no merge is necessary to authenticate to the source DB. Skip and you can skipto step 48.

that name, you can be sure that you are authenticating to the source token. Skipping this step is not harmful, it is only necessary if the application absolutely needs to know which token the following PK11_Authenticate() will be called on(for instance pwArg contains the actual password for the token). For most NSS applications the underlying password prompt system will properly disambiguate the appropriate password to the user(or it's password cache).