Files
android/libwvdrmengine/oemcrypto/odk/test/fuzzing
Rahul Frias 4532802ea0 Fix 1 ClangTidyBuild finding:
[ Merge of http://go/wvgerrit/145289 ]

* missing #include <string> for 'std::string' For more info see go/clang_tidy/checks/google3-build-missing-std-includes

This CL looks good? Just LGTM and Approve it!
This CL doesn’t look good? This is what you can do:
* Revert this CL, by replying "REVERT: <provide reason>"
* File a bug under go/clang-tidy-bug for category ClangTidyBuild if the change looks generally problematic.
* Revert this CL and not get a CL that cleans up these paths in the future by
replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to
opt out the respective paths in your CL Robot configuration instead:
go/clrobot-opt-out.

This CL was generated by CL Robot - a tool that cleans up code findings
(go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/METADATA.
Anything wrong with the signup? File a bug at go/clrobot-bug.

Tested:
    Local presubmit tests passed.

Bug: 224375138
Test: GtsTestCases on sunfish

PiperOrigin-RevId: 426761099
Merged from https://widevine-internal-review.googlesource.com/145250

Change-Id: I5a66b6eccc2b08ee11f92f90ce3b725f24c8d33c
2022-03-16 01:31:53 -07:00
..
2021-04-12 14:10:08 -07:00
2021-04-12 14:10:08 -07:00
2021-04-12 14:10:08 -07:00

ODK Fuzzing

Objective

  • Run fuzzing on ODK and KDO serialize and deserialize APIs using google supported fuzzer engines to find security vulnerabilities. Any issues found by clusterfuzz will be reported to odk fuzz buganizer.

Run fuzz target on local machine

  • In order to run fuzz target locally and see code coverage, save binary input to be tested against fuzz target into a temporary corpus directory and execute following commands

    $ blaze build --config=asan-fuzzer //your:target
    $ blaze-bin/your/target FULL_CORPUS_DIR