No feedback if wrong password when importing cert

VERIFIED WORKSFORME

Status

Core Graveyard
Security: UI
P3
minor
VERIFIED WORKSFORME
18 years ago
2 years ago

People

(Reporter: Peter Janes, Assigned: Javier Delgadillo)

Tracking

1.0 Branch

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta2-])

(Reporter)

Description

18 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14-12 i686; en-US; m16) Gecko/20000602
BuildID:    2000060208

I attempted to restore a certificate exported from Netscape 4.73.  Mozilla
prompted for the password used to save the cert; when I entered the wrong one,
it continued as if nothing had happened (without importing the cert, of course).

Reproducible: Always
Steps to Reproduce:
1. Export a certificate from Netscape (or otherwise create a .p12 file).
2. Open the PSM.
3. Restore a cert, and select the .p12 file.  Type a wrong password.

Expected Results:  Should have reported that the password is incorrect, and re-
prompt.
(Reporter)

Updated

18 years ago
Component: Security: General → Daemon
Product: Browser → PSM
Version: other → 1.1
Reassigning to PSM.
Assignee: mstoltz → lord
QA Contact: czhang → lord
There's no way to confirm this bug until the new PSM is up.  I went through the
process of creating and exporting a certificate in NS4.x, so I can confirm this
bug once the new PSM is up.  Adding myself to cc: list and leaving it unconfirmed.

Comment 3

18 years ago
the new psm is up now, is it not?

Comment 4

18 years ago
Changing status to new.
Assignee: lord → dougt
QA Contact: lord → junruh

Comment 5

18 years ago
new
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 6

18 years ago
Reassigning all https/cartman/security bugs to valeski.  He will be finding new 
owner(s).  This shift is so that I can focus on embedding issues.  If the new 
owner has questions that can not be resovled, I may be able to lend a (quick) 
hand.

over to valeski....
Assignee: dougt → valeski

Updated

18 years ago
Target Milestone: --- → M17
Version: 1.1 → 1.2

Comment 7

18 years ago
This affects both Win32 and Linux.
Keywords: nsbeta2
OS: Linux → All
Hardware: PC → All

Comment 8

18 years ago
Putting on [nsbeta2-] radar.
Whiteboard: [nsbeta2-]
(Assignee)

Comment 9

18 years ago
re-assigning to myself

Assignee: valeski → javi

Comment 10

18 years ago
Changing component.
Component: Daemon → Security: Crypto
Keywords: nsbeta2 → nsbeta3
Product: PSM → Browser
Target Milestone: M17 → M18
Version: 1.2 → other
Adding nsbeta2 keyword to bugs with nsbeta2 triage value in status field so the 
queries don't get screwed up
Keywords: nsbeta2

Comment 12

18 years ago
Worksforme with the 8/21 Linux and WinNT builds.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → WORKSFORME

Comment 13

18 years ago
Verified with the 8/22 WinNT and Linux builds.
Status: RESOLVED → VERIFIED

Comment 14

17 years ago
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: M18 → ---
Version: other → 2.1

Comment 15

17 years ago
Mass changing Security:Crypto to PSM

Updated

13 years ago
Component: Security: UI → Security: UI
Product: PSM → Core

Updated

10 years ago
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.