Keith Whaley wrote:
KaiRo - Robert Kaiser wrote:
Keith Whaley schrieb:
I have a feeling I might want to know a litle more detail about that
last sentence.
Would you kindly elaborate on "...we always encrypt, but default
generate a key from an empty master password."?
Well, I'm not an expert on the password manager, I'm just a mere project
coordinator, localizer and build engineer in the project, and esp. the
first function I've listed makes me into someone who mostly knows
headlines only, but on the other hand knows those from the whole project
and has an overview. Still, what I don't have is a deep view into those
things, others are better there.
In any case, we're using the exact same password manager in SeaMonkey
2.0 as in Firefox 3.5, and it always goes through the encryption
mechanism when storing passwords (and eventually migrated obscured
passwords from 1.x get re-encrypted in chunks when the computer is
idle). By default, it uses an empty master password for the encryption
algorithm though, and doesn't prompt for that one.
This should be the same as what SeaMonkey 1.x did when you chose to
encrypt passwords but didn't set a master password. What it did with the
"obscuring" option is not supported an more though, even though we can
read passwords in that format and import them.
Robert Kaiser
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
