Some users of SeaMonkey 2.0b1 who have migrated from SeaMonkey 1.1.17 have been complaining that the resulting profile claims to have a master password. As I understand it, NSS uses the key3.db to tell whether or not a master password exists, and we do nothing more than copy the file during migration, so I am at a loss to explain why this might happen. At least one of the reporters has confirmed that his original profile has no master password. See bug 506638 for the gory details.

--
Warning: May contain traces of nuts.
--
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to