Stop deleting key3.db in Firefox init
Categories
(Core :: Security: PSM, enhancement, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox86 | --- | fixed |
People
(Reporter: KaiE, Assigned: keeler)
References
Details
(Whiteboard: [psm-assigned])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Now that you have completely removed support for key3.db, by disabling DBM in bug 1594931, firefox is no longer able to perform a migration from key3.db to key4.db
Consequently, I think you can stop cleaning up key3.db.
If a user previously used firefox 57 (pre bug 783994), and directly executes firefox 73+ on that profile, you probably don't want to delete the user's key3.db because it wasn't yet migrated.
If the user already ran 63+ on that profile, you had already deleted the key3.db file (bug 1475775).
|
Reporter | |
Updated•5 years ago
|
|
||
Comment 1•5 years ago
|
||
We should have a release watershed at Firefox 72 to prevent dataloss.
Moreover, key3.db may not be removed even if migration has done due to bug 1607652.
|
|
||
Updated•5 years ago
|
|
Assignee | |
Updated•5 years ago
|
|
|
Assignee | |
Comment 2•4 years ago
|
||
As of bug 1594931, Firefox does not migrate old NSS DB files to the newer
version. As a result, any old NSS DB files that exist in the profile directory
either were already migrated or will never be migrated. To avoid data loss,
this patch removes the functionality that would remove key3.db if it existed in
the profile directory.
|
||
Updated•4 years ago
|
|
|
Assignee | |
Updated•4 years ago
|
|
||
Comment 4•4 years ago
|
||
| bugherder | ||
Description
•