On 11/1/2009 11:12 PM, Chris Ilias wrote:
> On 09-11-02 1:48 AM, Rufus wrote:
>> Phillip Jones wrote:
>>> David E. Ross wrote:
>>>
>>>> There is a serious inconsistency in how Password Manager works. See bug
>>>> #525737 at<https://bugzilla.mozilla.org/show_bug.cgi?id=525737>.
>>> Sounds like from reading Bug(s) that the developers are considering
>>> removing the the line sound like based on what I am reading you won't
>>> be able to save passwords and user names. If so we'll need a three
>>> ring binder or notepad just to save all the user names and passwords
>>> you have to keep up with. the all the CC companies. the bank. And the
>>> institution I have my mutual fund with, including all the forums, and
>>> newsgroups,I'd have to have a pretty good size note book.
>> ...if they remove the Password Manager I'll go back to 1.1.18 and STAY
>> there...
>>
>> ...or start using another app altogether.
>
> I've read the two bugs. Where in
> <https://bugzilla.mozilla.org/show_bug.cgi?id=525737> or
> <https://bugzilla.mozilla.org/show_bug.cgi?id=425145> is there talk
> about removing the ability to save any passwords?
>
The question is really about passwords that are truly important (e.g.,
for logging-on to SSL-secure sites for financial transactions). Some
such sites attempt to block the use of any password manager, instead
requiring the user to manually input the user ID and password.
With SM 1.1.x, I was able to put
user_pref("wallet.crypto", true);
user_pref("wallet.crypto.autocompleteoverride", true);
into my user.js file. For most (not all) cases, this overrode the
site's blocking.
Wallet is no longer used by Password Manager; instead, Satchel is used.
Bug #425145 contains a discussion about whether or not to honor a
site's blocking of Password Manager. That is, whether to allow users to
override that blocking. The discussion in that bug report, however,
confuses me; I cannot tell if any conclusion was reached.
Thus, the questions are:
1. Do the wallet.crypto and wallet.crypto.autocompleteoverride
preference variables still allow use of Password Manager in SM 2 for
sites that block that use?
2. If not, does the capability exist in SM 2? If so, what preference
variables should be set?
--
David E. Ross
<http://www.rossde.com/>
Go to Mozdev at <http://www.mozdev.org/> for quick access to
extensions for Firefox, Thunderbird, SeaMonkey, and other
Mozilla-related applications. You can access Mozdev much
more quickly than you can Mozilla Add-Ons.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
