Closed Bug 57154 Opened 25 years ago Closed 25 years ago

expired web server certificate shows as verified.

Categories

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

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

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
psm2.0

People

(Reporter: nitinp, Assigned: ddrinan0264)

References

(
URL
)

Details

(Whiteboard: [rtm-])

Install the latest MN6 daily build. Go to the above mentoined url - https://junruh.mcom.com:32040/tests.html After successfully negotiating the SSL ,click the lock icon to open the SA. View the certificate from the view button in the Selected Item Tab. The certificate has expired on Jul 06 2000 and it still says that it has been verified.
adding keyword rtm
Keywords: rtm
Summary: expired web server certificate shows as verified. → expired web server certificate shows as verified.
The same thing occurs with WinNT 4.76 with PSM.
Can you also use the cert somewhere that it's supposed to fail? What negative side-effect is there beyond lying about the validity of the cert? If there are no side-effects, I would be tempted to rtm- this.
Whiteboard: [need info]
When you first visit the site, you have to ask PSM to: "Accept this certificate anyway for this session" PSM takes that into account when you view the cert. So while I agree that the wording may be a little misleading, it's not really a bug that needs fixing for this version.
Whiteboard: [need info] → [rtm-]
changing QA contact to junruh@netscape.com
QA Contact: nitinp → junruh
nsbeta1
Keywords: nsbeta1
PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: --- → 2.0
Version: other → 2.0
Marking fixed. Tested on 5/14 WinNT Mozilla.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.