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.
Having experimented with upgrading from 2.49.5 to 2.53.1 in a Linux Mint
VM today...
- Deleting key3.db and cert8.db doesn't seem to result in losing any
data (I wasn't sure just reading the release notes). On first start,
2.53.1 creates two new files key4.db and cert9.db, presumably containing
the same data but in the new format. The upgrade seems to remove the
old key3.db anyway, and deleting cert8.db doesn't seem to lose anything
(all my saved passwords are still there, and nothing noticeably missing
from the Certificate Manager).
- 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).
- I also tried just starting the new version without first removing the
master password in 2.49.5 (against the advice of the release notes). As
others have mentioned, that also seemed to work fine - provided you
enter the master password when prompted on first starting 2.53.1. If
you cancel that prompt and exit SeaMonkey, next time there is no prompt
for the master password and all the passwords are gone! I wouldn't
recommend going against the advice of the release notes though; this was
just out of interest, working with a copy of my profile which I didn't
mind trashing. Although it seemed to work for me, there might be some
issue I haven't noticed, and for all I know it might also depend on the
OS, exactly which version the upgrade is from, installed extensions,
configuration settings, the day of the week...
I will, of course, be backing up my profile before upgrading SeaMonkey
on my live system!
--
Mark.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
