Files

Ronish Kalia d0f454d91c [DON'T BLOCK] Test ownership migration rules

This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.

For more details please refer to the link below,
<add g3 doc link>

Bug: 304529413
Test: N/A
Change-Id: I204c137da43a021bcebe316759d1aadaec99fe2a

2024-02-14 14:19:08 +00:00

corpus/little_endian_64bit

Merge Android odk fuzz changes(Adding corpus) from http://go/wvgerrit/98692

2020-04-27 14:00:17 -07:00

corpus_generator

[DON'T BLOCK] Test ownership migration rules

2024-02-14 14:19:08 +00:00

Android.bp

[DON'T BLOCK] Test ownership migration rules

2024-02-14 14:19:08 +00:00

odk_fuzz_helper.cpp

Allow server to send license with larger ODK_MAX_NUM_KEYS

2024-01-29 12:31:03 -08:00

odk_fuzz_helper.h

Merge latest oemcrypto-v17 change

2022-01-27 20:07:15 -08:00

odk_fuzz_structs.h

Update license comment

2021-04-12 14:10:08 -07:00

odk_license_request_fuzz.cpp

Update license comment

2021-04-12 14:10:08 -07:00

odk_license_response_fuzz_with_mutator.cpp

Update license comment

2021-04-12 14:10:08 -07:00

odk_license_response_fuzz.cpp

Update license comment

2021-04-12 14:10:08 -07:00

odk_provisioning_request_fuzz.cpp

Update license comment

2021-04-12 14:10:08 -07:00

odk_provisioning_response_fuzz_with_mutator.cpp

Fix unused param warnings in oemcrypto fuzz test

2021-04-23 10:11:48 -07:00

odk_provisioning_response_fuzz.cpp

Update license comment

2021-04-12 14:10:08 -07:00

odk_renewal_request_fuzz.cpp

Update license comment

2021-04-12 14:10:08 -07:00

odk_renewal_response_fuzz_with_mutator.cpp

Fix unused param warnings in oemcrypto fuzz test

2021-04-23 10:11:48 -07:00

odk_renewal_response_fuzz.cpp

Update license comment

2021-04-12 14:10:08 -07:00

README.md

Copy submitted odk fuzzing changes from cdm repository to android

2020-04-21 18:42:43 +00:00

README.md

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
```