You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you discover a potential security issue in s2n we ask that you notify
AWS Security via our vulnerability reporting page. Please do not create a public github issue.
Problem:
#4960 introduces coverage report generated by running fuzz tests. This is an aggregate report that merges multiple coverage reports into one. Therefore the report does show high-level insight like "How many % of s2n-tls code is covered/reached by fuzzer" and "Which areas of code are missing fuzzer coverage".
However, when we write individual fuzz tests, we do not intend to fuzz test the entire repo. Instead, each test has its own "target functions", which we intend to fuzz test. We currently are missing explicit coverage of such "target functions".
Solution:
Generate new report/metric on individual fuzz tested functions. Each fuzz test has a comment at the top of the file to indicate which functions are targeted. For example,
metric/report should show how many % of the target function is covered by the fuzz test. This can be extracted from llvm's coverage report.
the solution needs to be locally testable so that when we write new fuzz tests, we know target functions are effectively fuzzed
metric/report should be stored for future access. scheduled fuzz test will be a good place to perform data upload
both old & new fuzz tests need to follow the convention to include target functions in a format so they can be easily parsed when identifying list of target functions
The text was updated successfully, but these errors were encountered:
Security issue notifications
If you discover a potential security issue in s2n we ask that you notify
AWS Security via our vulnerability reporting page. Please do not create a public github issue.
Problem:
#4960 introduces coverage report generated by running fuzz tests. This is an aggregate report that merges multiple coverage reports into one. Therefore the report does show high-level insight like "How many % of s2n-tls code is covered/reached by fuzzer" and "Which areas of code are missing fuzzer coverage".
However, when we write individual fuzz tests, we do not intend to fuzz test the entire repo. Instead, each test has its own "target functions", which we intend to fuzz test. We currently are missing explicit coverage of such "target functions".
Solution:
Generate new report/metric on individual fuzz tested functions. Each fuzz test has a comment at the top of the file to indicate which functions are targeted. For example,
s2n-tls/tests/fuzz/s2n_client_fuzz_test.c
Lines 16 to 18 in 0fef0f5
Requirements / Acceptance Criteria:
The text was updated successfully, but these errors were encountered: