Closed Bug 1644423 Opened 5 years ago Closed 5 years ago

[migration] It's not possible to open NSS DBM db with NSS_DISABLE_DBM

Categories

(NSS :: Libraries, enhancement)

3.53
enhancement

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: slev, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

  1. Create NSS legacy DB(DBM) in /etc/pki/nssdb
  2. rebuild/upgrade NSS to NSS with NSS_DISABLE_DBM
  3. NSS_InitContext("/etc/pki/nssdb", NULL, NULL, NULL, NULL, NSS_INIT_READONLY)

Actual results:

NSS_InitContext fails with SEC_ERROR_LEGACY_DATABASE.

Expected results:

For now, ALTLinux(one of the Linux distro) defaults DBM.
We plan to build NSS without DBM support.

How to migrate DBM to SQL in this case (NSS_DISABLE_DBM)?
The process described here: https://bugzilla.mozilla.org/show_bug.cgi?id=1415912
assumes a build with DBM. The situation when a user has had DBM and then, tomorrow he will have only SQL is real.

I think some transition flag should exist which will allow the implicit or explicit migration, but forbid to create a new NSS db with legacy type.

It won't be possible to migrate away from DBM using a build without DBM. You'll need to use a build of NSS with DBM enabled to perform the migration.

The process described at the Fedora wiki is the best way forward, but you'll need to recompile with DBM support until you've completed the migration

Status: UNCONFIRMED → NEW
Ever confirmed: true

I see, there is no choice but to keep the legacy db type.
Thank you.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.