Closed
Bug 1578186
Opened 5 years ago
Closed 5 years ago
Add fuzzing support for HTTP2 proxy functionality in Necko fuzzing layer
Categories
(Core :: Networking: HTTP, enhancement, P1)
Tracking
()
RESOLVED
FIXED
mozilla71
People
(Reporter: decoder, Assigned: decoder)
References
Details
(Keywords: sec-want, Whiteboard: [necko-triaged][post-critsmash-triage][adv-main71-])
Attachments
(1 file)
There is a substantial amount of code for handling HTTP2 connections over an HTTP2 proxy that cannot be fully tested with the current fuzzing target. Adding support for this involves modifying the fuzzing target to use a proxy, but we also need to modify TLSFilterTransaction to skip the TLS layer entirely (skip encryption/decryption) for the inner (proxied) connection.
|
Assignee | |
Comment 1•5 years ago
|
||
|
||
Updated•5 years ago
|
Whiteboard: [necko-triaged]
|
||
Comment 2•5 years ago
|
||
https://hg.mozilla.org/integration/autoland/rev/23b87ee261473684f5ec8c90dbeede7ed927658f
https://hg.mozilla.org/mozilla-central/rev/23b87ee26147
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
|
||
Updated•5 years ago
|
status-firefox69:
--- → wontfix
status-firefox-esr60:
--- → wontfix
status-firefox-esr68:
--- → wontfix
|
||
Comment 3•5 years ago
|
||
Christian, do you think this bug requires manual verification? If so please update the flag.
Flags: qe-verify-
Flags: needinfo?(choller)
Whiteboard: [necko-triaged] → [necko-triaged][post-critsmash-triage]
|
|
Assignee | |
Comment 4•5 years ago
|
||
No, this bug is adding a fuzzing feature, not fixing a defect.
Flags: needinfo?(choller)
|
||
Updated•5 years ago
|
Whiteboard: [necko-triaged][post-critsmash-triage] → [necko-triaged][post-critsmash-triage][adv-main71-]
|
||
Updated•3 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•