Closed Bug 194523 Opened 21 years ago Closed 21 years ago

Cannot set Master Password

Categories

(SeaMonkey :: Passwords & Permissions, defect)

x86
Windows 2000
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 192917

People

(Reporter: phb1949, Assigned: dveditz)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210

This is happening both from my system (W2k) and from my wife's [W98SE]. When I
try to set the masster password, I get the message "Cannot Change Master
Password". Also on the Tools Menu/Password Manager, there is not an entry for
Master Password. I have tries this from my own account and as the administrator.
Also, resetting the Master Password does not affect this problem. 

Reproducible: Always

Steps to Reproduce:
1.Select Edit/Preferences/Privacy & Security/Master Password
2.Click Change Password
3. The "Generic Crypto Services" is selected. "Current Password" contains (not
set) and is dimmed.
4. Enter a passowrd in "New password"
5. Enter same password in "New password Again". The OK button is no longer dim
6. Click OK

Actual Results:  
An Alert Box appears with "Unable to change master password".
FYI, trying to change the "encription" setting in the Passwords Tab, causes the
same dialog box to appear and I get the same results.

Expected Results:  
I should be able to enter a master passord.

I installed version 1.2 on this machine in January and have since upgrated to
1.3a and 1.3b. As mentioned earlier, restting the Master Password, doesn't help.
I still can't set it. I was abled to use this feature in earlier versions of
Mozilla (Prioe to January, I was running 1.2 on Windows ME with no problem).

*** This bug has been marked as a duplicate of 192917 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
QA Contact: tpreston → gbush
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.