![]() This scenario cannot happen with the firefox and nss packages that weĭistribute on RHEL 6 and RHEL 7, because we don't migrate to sql. In other words, the issue is that an unprotected backup file remains in With this scenario, the new sql storage (key4) is password protected,īut the pre-migration storage (ke圓) remains unprotected. ![]() user upgrades to a thunderbird that uses sql by default, The upstream report depends on the following series of events: It seems that NSS in RHEL is configured differently from the upstream version and this might be causing the problem. Then it creates the new NSS files (key4.db and cert9.db). If I run firefox after setting the following environment variable: Even with a fresh Firefox profile, it still creates a ke圓.db file. However, from my tests, it seems that in the RHEL version of Firefox, the NSS files (ke圓.db, cert8.db and secmod.db) are never upgraded to the newer versions. The upstream bug mentioned above was due to the fact that Firefox left the old ke圓.db file when it upgraded it to key4.db. This is almost certainly related to bug 1625531. It is used to encrypt the usernames and passwords in signons.sqlite. If the old ke圓.db file is restored, it will work again, but only the first time, after which the file is deleted again. Although file shows ke圓.db to be in Berleley DB 1.85 format, it isn't the case. The logins.json file remains intact, but the key needed to decrypt the usernames and passwords is lost. ![]() If the file is present on startup, it will correctly load the saved logins, but it will then delete the ke圓.db file and the next time Firefox is run, there will be no saved logins (and no master password set). What seems to be happening is that the ke圓.db file gets deleted when Firefox is launched.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |