44291 - Getting new-password dialog instead of change-password dialog

Status: VERIFIED WORKSFORME

(Core Graveyard :: Security: UI, defect, P3)

Description

[Stephen P. Morse]

Under the following scenario I get the new-password dialog (does not ask for old 
password) even though I asked for a change of password.

1. Create a new profile and bring up the browser
2. Go to http://people.netscape.com/morse/password.htm
3. Fill in any arbitrary username and password, then submit form
4. Answer "yes" to the "do you want to save" dialog
5. Dismiss the encryption-disclaimer dialog
6. Dismiss the security-alert dialog
7. From the menu select tasks->privacy->password-manager->encrypt
8. PSM dialog for creating master password appears.  Enter password and press OK
9. Security alert appears (this is bug 44044).  Click OK
10. Security alert appears again (more bug 44044).  Click OK again.
11. From the menu select tasks->privacy->password-manager->change-password

The dialog that appears now has text fields for "new password" and "new pasword 
(again)".  It does not have a text field for "old password" which is supposed to 
be on the change-password dialog.  So this is the new-password dialog instead of 
the old-password dialog.  Furthermore, if I enter a new password, it apparently 
does nothing -- the password does not get changed.

I believe that if I exit and then reenter the browser, and then try to change 
the password, that I will get the correct change-password dialog.

Comment 1

[Jay Patel [:jay]]

Putting on [nsbeta2+] radar for beta2 fix. 

Comment 2

[leger]

Per beta2 triage, moving from [nsbeta2+] to [nsbeta2-], putting on nsbeta3 
nominee radar.

Comment 3

[Terry Hayes]

This appears to be caused by the client caching the content of PSM dialogs.
Changing PSM to set Pragma: no-cache on the HTTP results fixes this bug.

Checkin is pending for this.

Comment 4

[John Unruh]

Worksforme. This appears to be fixed.

Comment 5

[Terry Hayes]

Well, since I didn't check in the change, I don't know why this problem would 
have disappeared.  Is anyone aware of changes in the Mozilla caching methods 
that would have corrected this problem?

Comment 6

[John Unruh]

Verified worksforme.

Comment 7

[John Unruh]

Mass changing Security:Crypto to PSM

Comment 8

[John Unruh]

Mass changing Security:Crypto to PSM