Closed Bug 82437 Opened 23 years ago Closed 23 years ago

Lock unlocked at secure site

Categories

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

1.0 Branch
x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED
psm2.0

People

(Reporter: junruh, Assigned: ddrinan0264)

References

(Depends on 1 open bug, )

Details

(Whiteboard: PDT+; needs qa)

1.) Visit https://www.verisign.com/ This site contains some insecure 
information.
What happens: The lock is unlocked, but page info shows that the site is secure.
What is expected: A lock icon with a slash showing that the site contains mixed 
content.
Confirmed.

Target -> 2.0
P1 (this is basic SSL functionality)

The Page Info text should also show that there is mixed content, but it does not.

Priority: -- → P1
Target Milestone: --- → 2.0
A reproducible testcase is to go down the list on 
http://junruh.mcom.com/ciphers.html . Before long, as you visit these secure 
sites, you will see that the lock is unlocked.

*** This bug has been marked as a duplicate of 82736 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Reopening. Not really a dupe.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
PDT for PSM
Whiteboard: PDT
PDT+ as per Steve Elmeer 6/20/2001
Whiteboard: PDT → PDT+
Whiteboard: PDT+ → PDT+; eta 6/22
What's the current status of this bug?
David is working hard on the issue.
whiteboard-> not ready
Whiteboard: PDT+; eta 6/22 → PDT+; eta 6/22 not ready
Adding lord and ssaux to cc-list.

The current scheme is that PSM gets notifications when frames load but *not* 
when images load. This means that an insecure frame in a secure site will cause 
a mixed content warning to be displayed and the lock icon will be set with a 
strike through it. An insecure image on a secure site will not generate a mixed 
content warning message and the lock icon will be set to locked.

Is this acceptable? Or should insecure images display the mixed content 
warnings?
This behavior is acceptable to me.  

John Unruh, please qa this behavior.


Whiteboard: PDT+; eta 6/22 not ready → PDT+; needs qa
Marking fixed. The lock behavior is as desired.
Status: REOPENED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → FIXED
*** Bug 76168 has been marked as a duplicate of this bug. ***
Verified.
Status: RESOLVED → VERIFIED
Depends on: 82458
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.