Closed Bug 56857 Opened 25 years ago Closed 25 years ago

Change personal security password does not work properly

Categories

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

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 71805

People

(Reporter: nitinp, Assigned: ddrinan0264)

Details

(Whiteboard: [rtm-])

Install the latest netscap6 and start a profile. Choose the "Change personal security password" from Tasks|Prviacy and security". Enter the wrong passwords and click OK. actual result - The window closes , giving the user the feeling that the password has been changed. expected result - some warning should come up saying that the passwords are not correct and certainly the window should not close.
adding keyword rtm.
Keywords: rtm
Summary: Change personal security password does not work properly → Change personal security password does not work properly
Worksforme. I get a dialog box stating "Could not set your personal security password. 10/18 WinNT trunk build.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Reopening. Win98 and Linux 10/24 branch commercial build. I see it happening exactly as nitinp described it. On the branch builds, there is no longer a follow up dialog box stating "Successfully set your new password" or "Could not set your password".
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Any update for this bug? Time's basically gone, but this looks important.
Whiteboard: [need info]
Given the fact that this is the result of the user entering the *wrong password* and that in this case the user shouldn't be able to change, I think that this is not a stopper. Recommend minus.
rtm-, not stopper.
Whiteboard: [need info] → [rtm-]
changing QA contact to junruh@netscape.com
QA Contact: nitinp → junruh
Worksforme with the 12/21 Win Mac and Linux commerical trunk builds.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → WORKSFORME
Reopening. This is still happening if you don't enter the old password correctly.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
*** This bug has been marked as a duplicate of 71805 ***
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → DUPLICATE
Verified dupe.
Status: RESOLVED → VERIFIED
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.