Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Disable "Saved passwords" button

  • 3 replies
  • 1 has this problem
  • 3 views
  • Last reply by simopal6

more options

Basically, I would like users not to be able to view saved passwords.

According to https://support.mozilla.org/en-US/questions/1206446, the pref.privacy.disable_button.view_passwords option should do the trick. However, whatever I set it to, there's just no difference. When I set it to true, the "Saved passwords" button is enabled, and when I click it I notice (by manually checking the pref.js file) that the value changes to false (it only changes when I click on the button; before that, the value is still true). If I set it to false, the button still works (but I guess that's the wrong value for my purposes, since the preference name seems to imply the action of disabling the button).

I have no idea how the guys from the question mentioned above managed to disable the button. They seem to use a different configuration syntax ("pref.privacy.disable_button.view_passwords;0") than the one needed for the pref.js file, and also mention "locking" it, but I don't know which file I should edit.

I'm using Thunderbird 60.4.0, 64 bit, Linux,

Thanks for your help!

Basically, I would like users not to be able to view saved passwords. According to https://support.mozilla.org/en-US/questions/1206446, the pref.privacy.disable_button.view_passwords option should do the trick. However, whatever I set it to, there's just no difference. When I set it to true, the "Saved passwords" button is enabled, and when I click it I notice (by manually checking the pref.js file) that the value changes to false (it only changes when I click on the button; before that, the value is still true). If I set it to false, the button still works (but I guess that's the wrong value for my purposes, since the preference name seems to imply the action of disabling the button). I have no idea how the guys from the question mentioned above managed to disable the button. They seem to use a different configuration syntax ("pref.privacy.disable_button.view_passwords;0") than the one needed for the pref.js file, and also mention "locking" it, but I don't know which file I should edit. I'm using Thunderbird 60.4.0, 64 bit, Linux, Thanks for your help!

Modified by simopal6

All Replies (3)

more options

set the value via 'Config editor' button pref.privacy.disable_button.view_passwords;0 Click on OK

Restart Thunderbird

However, that does not stop anyone from changing it back using the same process you used to set it.

Alternative: Something you could use is this: If you wanted to hide the Show Password button. Exit Thunderbird. Create a 'chrome' folder in the profile name folder and then create a 'userChrome.css' file using a text editor like Notepad, that contained the following.


/*
* Do not remove the @namespace line -- it's required for correct functioning
 */

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");

/*Hide the 'Show Passwords' button*/
#togglePasswords { display: none !important; }

Then save 'userChrome.css' file in 'chrome' folder. Start Thunderbird and check the 'Saved Passwords' window.

However, a user could edit or delete that file, or (if they don't understand how you disabled it) just transfer their data to a new profile. Assuming they would know how to do it.

Modified by Toad-Hall

more options

The alternative option I mentioned in previous comment is probably a bit more difficult for the average user to meddle with. When you see a disabled button, it might encourage someone to find a way of enabling it, but if the button does not exist in the first place, they may assume that is the normal thing. The 'userChrome.css' file can easily be copy pasted into any 'profile name' folder if you need to reproduce it in more than one 'profile name' folder.

more options

Thanks, your second suggestion works perfectly, and I agree with your reasoning.

However, it justs annoys me that I can't get it to work with the config editor.

I tried setting pref.privacy.disable_button.view_passwords to boolean false, boolean true, string 0, string 1, but nothing seems to work.

I'm not sure if by "pref.privacy.disable_button.view_passwords;0" you mean that I should set its value to 0, or to string "pref.privacy.disable_button.view_passwords;0", or even if I should create a key named "pref.privacy.disable_button.view_passwords;0" (which doesn't make sense, I know). Anyway, I tried even those possibilities, but still no success.