Closed
Bug 51915
Opened 24 years ago
Closed 24 years ago
SMIME: getting thawte cert send lock into a frenzy
Categories
(Core Graveyard :: Security: UI, defect, P3)
Tracking
(Not tracked)
People
(Reporter: nitinp, Assigned: ddrinan0264)
Details
(Whiteboard: [nsbeta3-][pdtp3])
if you don't have a thawte acct , use US-545-11-1111-1 and password "netscape".
when you go thru the steps observe the lock . So the pages are obviously sslified.
When each subsequent page is loading the lock is open ( the page is still
secure). When the seure page is loaded , the lock is broken and not locked.
even the mouse over tooltip does not indicate security information.
Bad for SSL . Must be fixed for PSM 1.3. there are a bunch of bugs on the lock ,
but I just wanted to create a different one to track this separately.
adding keyword nsbeta3 and nominating for nsbeta3+
Keywords: nsbeta3
Whiteboard: [nsbeta3+]
Assignee | ||
Comment 2•24 years ago
|
||
Adding jgmyres@netscape.com
John,
Any idea why this is happening?
Comment 4•24 years ago
|
||
According to junruh, thawte is for smime. We're not doing smime now, PDTP3.
Priority: P2 → P3
Whiteboard: [nsbeta3+] → [nsbeta3+][pdtp3]
Target Milestone: --- → Future
per PDT: P3-P5 priority bugs changed from nsbeta3+ to nsbeta3- since we have
more important work to do for Seamonkey. If you disagree, please state your case
in the bug report and nominate for rtm. Thanks.
Summary: getting thawte cert send lock into a frenzy → SMIME: getting thawte cert send lock into a frenzy
Whiteboard: [nsbeta3+][pdtp3] → [nsbeta3-][pdtp3]
Comment 6•24 years ago
|
||
*** This bug has been marked as a duplicate of 47496 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Comment 8•24 years ago
|
||
Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Target Milestone: Future → ---
Version: other → 2.1
Comment 9•24 years ago
|
||
Mass changing Security:Crypto to PSM
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•