[email protected] wrote:
Steve Dunn wrote:
On 2020-03-05 15:17, Frank-Rainer Grahl wrote:
Check the password manager in the upgraded install. At least until recently
this didn't work.
I tested only on Windows and left the new password blank e.g no chars
entered. This worked fine for me.
Can a master password be set after the upgrade has been completed, or
must all saved passwords be left insecure until whenever this bug is fixed?
The release notes don't actually say - they just say you have to remove the
master password before upgrading and them delete two files with unencrypted
passwords in them after upgrading.
The way I interpret it is not that it's a bug, but that the format of the
files is changed in the new version and can't be converted on first use of the
new version if a master password is set.
Correct. Thunderbird did track this in
https://bugzilla.mozilla.org/show_bug.cgi?id=1510212
I am not sure if it has been fully solved but the issue does not occur if the
master password is removed before migration so we still think this is the best
way. You can set it afterwards and now with a better encryption. Just make
sure to delete the old key3.db and cert8.db.
- There doesn't seem to be any problem setting a master password in 2.53.1
once the profile has been converted. Having done so, I assume it is actually
encrypting the saved passwords (though it would be good to have that confirmed).
Yes and hopefully with better encryption.
I will, of course, be backing up my profile before upgrading SeaMonkey on my
live system!
That is really recommended.
FRG
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
