Closed
Bug 490361
Opened 16 years ago
Closed 14 years ago
SSLStatus.cipherName not accessible with "partial encryption"
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: sivennol, Unassigned)
Details
(Whiteboard: [CLOSEME 2010-11-15])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10
On a page with "partial encryption, the SSLStatus attributes cipherName and secretKeyLength expire after a short period (10-15 seconds or so, before they resolve to "null").
I have an extension that relies on these attributes, and I don't believe that because the content is "mixed," that the cipher name and keysize (eg. "AES-256") for the base of the page should be completely inaccessible to developers.
They are already hidden on a "Page View" of a mixed-content page, so normal users would not see them, which does make sense.
Reproducible: Always
Steps to Reproduce:
1. Query gBrowser.securityUI.QueryInterface(ci.nsISSLStatusProvider).SSLStatus.cipherName on an SSL mixed-content page.
2. Wait 10-30 seconds.
3. Attempt to query it again.
Actual Results:
On the first query, cipherName returns (for example) "AES-256"
On the second result, cipherName returns null.
Expected Results:
Returns "AES-256" always, as that is the cipher of the base of the page, regardless of mixed-content status
I'm not proposing that the UI change for end-users, just that I should be able to access the data from an extension.
Sorry, forgot to mention:
ci in the query should be Components.interfaces
Comment 2•15 years ago
|
||
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles. If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.
This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
Comment 3•14 years ago
|
||
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•