Closed
Bug 1804460
Opened 1 year ago
Closed 1 year ago
Add detailed connection info to WebRequests API and DevTools
Categories
(Core :: Security: PSM, enhancement, P1)
Core
Security: PSM
Tracking
()
RESOLVED
FIXED
112 Branch
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: djackson, Assigned: djackson)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-needed, Whiteboard: [addons-jira])
Attachments
(3 files)
We should expose more information about how the connection was established, e.g.
- Did it use Encrypted Client Hello?
- Did it use DNS-over-HTTPS?
- Did it use Delegated Credentials?
- Did it use OCSP?
This information will be available to addons via getSecurityInfo and displayed in the security panel for DevTools connections.
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Attachment #9307071 -
Attachment description: WIP: Bug 1804460 - Add detailed connection info to WebRequests and DevTools. → WIP: Bug 1804460 - Add detailed connection info to DevTools Security Tab.
It would be very useful if, when ECH is enabled, the plaintext SNI and the encrypted SNI are displayed as well. (Since OUTER is sent in plaintext, it would be good to know what is encrypted inside the INNER payload.)
Comment 4•1 year ago
|
||
We'll need to update the MDN docs: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/webRequest/SecurityInfo
Keywords: dev-doc-needed
Comment 5•1 year ago
|
||
Depends on D164092
Updated•1 year ago
|
Whiteboard: [addons-jira]
Updated•1 year ago
|
Pushed by djackson@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a6f38e27ecbf Add detailed connection info to WebRequest GetSecurityInfo API. r=keeler,devtools-backward-compat-reviewers,willdurand https://hg.mozilla.org/integration/autoland/rev/20e4e0b6a005 Add a smoke test. r=robwu,djackson
Comment 7•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a6f38e27ecbf
https://hg.mozilla.org/mozilla-central/rev/20e4e0b6a005
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•