John wrote:
David E. Ross wrote:
On 5/1/2009 12:38 PM, John wrote:
David E. Ross wrote:
On 4/24/2009 11:26 AM, John wrote:
The password manager in SeaMonkey doesn't always offer to save a password, depending on the site being visited. I have noticed in particular that it frequently won't save a password for a secure website having an https://... address. And yet this is not always the case. It will save the password for some secure sites. Is there any way to get it to save the passwords for all sites? Thanks!


John

I found that putting the following into the user.js file for my profile
significantly expands the scope of the Password Manager:
    user_pref("wallet.crypto", true);
    user_pref("wallet.crypto.autocompleteoverride", true);

Don't forget the semi-colon at the end of the line.  You must then
completely terminate SeaMonkey and then restart it for this to become
effective.

There will still be a few sites remaining where this doesn't work.
Also, nothing in SeaMonkey 1.1.x will help if the user ID and password
are entered in separate Web pages; I was told that the Password Manager
for SeaMonkey 2.x will indeed handle that situation.

After adding these two lines to my user.js file, I now am getting a popup "Change Master Password" (current password (not set)) every time I login where a password is being stored. I want to understand this better before I add a master password. I have never seen this popup before. Advice?

John

Someone else will have to answer this.  I've never seen this.

I added a master password. Now, anytime I go to a site where I have
stored a password, I get a popup asking me for the master password.
Strangely, if I click cancel instead of giving it the master password,
it still lets me login to the site with the stored password.

Apparently when I added those two lines to the user.js file, it caused
some other setting to change, because restoring the original user.js
file has failed to revert the browser's behavior to what it was before I
started messing with it.

John, when you add, or change a line, in user.js, the next time you start up SeaMonkey, user.js is incorporated into prefs.js which is the file that SeaMonkey actually uses to determine how it should work. Deleting user.js, or deleting lines from user.js, does not remove the lines from prefs.js!

I have backed up my profile and would like to try to get things back to
where they were. Before I try anything else, does SeaMonkey store any
settings anywhere other than in the profile, e.g. in the Windows Registry?


Make a back-up copy of prefs.js to somewhere else on your HD then use a text editor to open prefs.js, look for the lines that you entered into user.js and remove the lines from prefs.js

I notice in Firefox 3, there is a box under security to check or uncheck
top tell it if you want a master password. SeaMonkey doesn't seem to
have this, but I've seen the dire warning that if I reset the master
password all stored passwords will be lost.

The "Change Master Password" popup can be seen in SeaMonkey at
Edit->Preferences->Privacy and Security->Master Passwords->Change
Password. What will happen if I enter the current password in that form
and leave the boxes for "new password" blank?

John

Don't know, John, but as you know all your passwords, would any thing really be lost if you give it a go??

Daniel
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to