weak-crypto warning repeated on "open link in new window"

VERIFIED DUPLICATE of bug 156758

Status

Core Graveyard
Security: UI
P3
enhancement
VERIFIED DUPLICATE of bug 156758
17 years ago
a year ago

People

(Reporter: Jesse Ruderman, Assigned: Stephane Saux)

Tracking

1.0 Branch
Future
x86
Windows NT

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

17 years ago
1. Go to https://www.ecount.com/
Result: get a warning that the site uses weak crypto

2. Ctrl+click any link (or right-click and select "open link in new window")
Result: get another warning that the site uses weak crypto :(

Comment 1

17 years ago
Worksforme. The behavior is as designed. You can also turn off the warnings.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 2

17 years ago
Is this really "as designed"?  I can click on links within the window without
getting multiple warnings, but as soon as I ctrl+click a link within the site, I
get an extra warning.  Is there any security reason for showing the warning
twice when browsing using multiple windows but not when browing with one window?
 Is this a UI design decision that needs to be discussed in n.p.m.ui?
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

Comment 3

17 years ago
The "open link in new window" part of the bug appears to be fixed with the 6/20 
build. Reporter, can you try it again?
(Reporter)

Comment 4

17 years ago
I still see this bug in 2001 062004 on WinNT.
(Assignee)

Comment 5

17 years ago
moving to PSM
Component: Security: Crypto → Client Library
Priority: -- → P2
Product: Browser → PSM
Target Milestone: --- → 2.1
Version: other → 2.0
(Assignee)

Comment 6

17 years ago
p3
Priority: P2 → P3
(Assignee)

Updated

17 years ago
Keywords: nsenterprise
(Assignee)

Comment 7

17 years ago
Moving all P3 and P4 bugs targetted to 2.1 to future.
Target Milestone: 2.1 → Future
(Assignee)

Comment 8

17 years ago
removing nsenterprise keyword from PSM bugs with target milestone of future.
Keywords: nsenterprise

Comment 9

17 years ago
Mass assigning QA to ckritzer.
QA Contact: junruh → ckritzer

Updated

16 years ago
QA Contact: ckritzer → junruh

Comment 10

16 years ago
Marking works for me with the 4/11 branch Win2000 build, but while testing 
this bug, discovered and opened bug 136916.
Status: REOPENED → RESOLVED
Last Resolved: 17 years ago16 years ago
Resolution: --- → WORKSFORME

Comment 11

16 years ago
Reopening with new URL above. 
1.) Visit the link, then look under Miscellaneous testing for Low-grade 
security.
2.) Right click on the link and open another window.
What happens: As the original bug description states - "Result: get another 
warning that the site uses weak crypto."
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---

Comment 12

16 years ago
cc kaie
Assignee: ddrinan → ssaux
Status: REOPENED → NEW

Comment 13

16 years ago
In fact, the current implementation treats each open window as individual, each
window begins with the "unsecure" state, and therefore each window will again
show all warnings.

Therefore, I think this is not a bug, but a feature.

We should discuss, what the ideal behaviour is.

Should new windows, opened by "open in new window", inherit the current crypto
state of their parent window?
Severity: minor → enhancement

Comment 14

16 years ago
Since bug 136916 is a works for me, this bug should be marked the same way.
Status: NEW → RESOLVED
Last Resolved: 16 years ago16 years ago
Resolution: --- → WORKSFORME

Comment 15

16 years ago
Verified.
Status: RESOLVED → VERIFIED
(Reporter)

Comment 16

15 years ago
I don't understand why this bug was marked as WFM (what does this bug have to do
with bug 136916?).
Status: VERIFIED → REOPENED
Resolution: WORKSFORME → ---
(Reporter)

Comment 17

15 years ago

*** This bug has been marked as a duplicate of 156758 ***
Status: REOPENED → RESOLVED
Last Resolved: 16 years ago15 years ago
Resolution: --- → DUPLICATE

Comment 18

15 years ago
V
Status: RESOLVED → VERIFIED

Updated

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

Updated

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