New issue
Advanced search Search tips

Issue 599523 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug


Sign in to add a comment

Add fuzzers for the network stack

Project Member Reported by mmenke@chromium.org, Mar 31 2016

Issue description

The network stack has a lot of code to parse a variety of protocols.  We should create fuzzers for this code to help catch bugs.  This is intended as a metabug, to link net/ fuzzer-related bugs.
 

Comment 1 by eroman@chromium.org, Mar 31 2016

As a sub-task, we should also canonicalize the recommendations for file-naming / style, as was discussed on past reviews.

Comment 2 by mmenke@chromium.org, Mar 31 2016

Blockedon: 599525

Comment 3 by mmenke@chromium.org, Mar 31 2016

That's a good point - we may also want to come up with what-to-fuzz best practices.  For instance, we could fuzz SOCKS sockets in isolation, which I think we should do...but we could also fuzz an HTTP stream or HttpNetworkTransaction over a SOCKS proxy...  Don't think we want many integrationy tests, but not fuzzing HttpNetworkTransaction, for instance, seems like a mistake.

Comment 4 by eroman@chromium.org, Mar 31 2016

sgtm

Comment 5 by mmenke@chromium.org, Mar 31 2016

Blockedon: 599582

Comment 6 by mmenke@chromium.org, Mar 31 2016

Blockedon: 599584
Blocking: 600005
Blockedon: 600006

Comment 9 by mmenke@chromium.org, Apr 11 2016

Blocking: -600005
Blockedon: 600005
Blockedon: 602412
Blockedon: 602415
Blockedon: 602418
Blockedon: 602422
Blockedon: 602424
Blockedon: 602440
Blockedon: 602447
Blockedon: 602460
Blockedon: 606428
Project Member

Comment 22 by sheriffbot@chromium.org, Apr 13 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Available (was: Untriaged)
Labels: Network-Triaged

Sign in to add a comment