Closed
Bug 1331224
Opened 8 years ago
Closed 8 years ago
Spurious insecure password warning on Bugzilla
Categories
(Toolkit :: Password Manager, defect)
Toolkit
Password Manager
Tracking
()
RESOLVED
DUPLICATE
of bug 1329940
Tracking | Status | |
---|---|---|
firefox53 | --- | affected |
People
(Reporter: ekr, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file, 1 obsolete file)
646.73 KB,
image/png
|
Details |
No description provided.
Reporter | ||
Comment 1•8 years ago
|
||
Attachment #8826893 -
Attachment is obsolete: true
Reporter | ||
Comment 2•8 years ago
|
||
P.S. This was Nightly
Comment 3•8 years ago
|
||
From the screenshot I can see you were on enter_bug.cgi, what linked you to this page? If it was an insecure site then window.opener could have been insecure and this would be a dupe of bug 1329940.
Reporter | ||
Comment 4•8 years ago
|
||
I went to b.m.o and clicked "new".
Unfortunately, I can't repro it.
Flags: needinfo?(ekr)
Comment 5•8 years ago
|
||
I don't know why bugzilla.mozilla.org wouldn't be a secure context, but given this intermittent bug and others, I think we should switch to a more naive approach (isOriginPotentiallyTrustworthy) instead of using isSecureContext. See bug https://bugzilla.mozilla.org/show_bug.cgi?id=1329940. We can use isSecureContext in Nightly and debug issues and reports that come up there, until we are satisfied enough to use it in release.
Comment 6•8 years ago
|
||
(In reply to Tanvi Vyas - behind on bugmail [:tanvi] from comment #5)
> I don't know why bugzilla.mozilla.org wouldn't be a secure context, but
> given this intermittent bug and others, I think we should switch to a more
> naive approach (isOriginPotentiallyTrustworthy) instead of using
> isSecureContext. See bug
> https://bugzilla.mozilla.org/show_bug.cgi?id=1329940. We can use
> isSecureContext in Nightly and debug issues and reports that come up there,
> until we are satisfied enough to use it in release.
I don't have any reason to think this isn't caused by window.opener and therefore a dupe of bug 1329940. When the problem occurs we need to see the web console output for window.opener. In case you didn't know window.opener persists across top-level cross-origin loads so likely the tab in the screenshot was originally opened from an insecure context.
Comment 7•8 years ago
|
||
Duping to bug 1329940. Re-open if you can show that window.opener in your web console is secure.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•