commit | 2514c453f408e09a390e71af907831e77c62afdc | [log] [tgz] |
---|---|---|
author | Max Moroz <mmoroz@chromium.org> | Sat Nov 21 01:11:27 2020 |
committer | Copybara-Service <copybara-worker@google.com> | Sat Nov 21 01:26:04 2020 |
tree | b1a98a71b6abc469a166a186b4dba275f8c5da86 | |
parent | 2792639e6f1c9af9c7477f1f34996c9b3d0e6d3f [diff] |
Remove mmoroz@chromium.org from OWNER files. R=inferno@chromium.org TBR=dpranke@chromium.org Change-Id: I56d6684addf8e7f9c16dca2d963e01c0c8020b99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2553147 Reviewed-by: Abhishek Arya <inferno@chromium.org> Cr-Commit-Position: refs/heads/master@{#829902} GitOrigin-RevId: 596e04e2c128274a29e4a755b725e54f1e4a24db
Fuzzing is a testing technique that feeds auto-generated inputs to a piece of target code in an attempt to crash the code. It's one of the most effective methods we have for finding security and stability issues (see go/fuzzing-success). You can learn more about the benefits of fuzzing at go/why-fuzz.
This documentation covers the in-process guided fuzzing approach employed by different fuzzing engines, such as libFuzzer or AFL. To learn more about out-of-process fuzzers, please refer to the Blackbox fuzzing page in the ClusterFuzz documentation.
In Chromium, you can easily create and submit fuzz targets. The targets are automatically discovered by buildbots, built with different fuzzing engines, then uploaded to the distributed ClusterFuzz fuzzing system to run at scale.
Create your first fuzz target and submit it by stepping through our Getting Started Guide.
Creating a fuzz target that expects a protobuf instead of a byte stream as input.
Reproducing bugs found by libFuzzer/AFL and reported by ClusterFuzz.
Fuzzing mojo interfaces using automatically generated libprotobuf-mutator fuzzers.