2016-10-24 20:42:53 +00:00
|
|
|
# Frequently Asked Questions
|
|
|
|
|
|
2016-11-16 17:56:10 +00:00
|
|
|
## Why do you use a [different issue tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list) for reporting bugs in fuzz targets?
|
2016-10-24 20:42:53 +00:00
|
|
|
|
2016-11-16 17:56:10 +00:00
|
|
|
Security access control is important for the kind of issues that OSS-Fuzz detects.
|
2016-10-24 20:42:53 +00:00
|
|
|
We will reconsider github issue tracker once there are access control
|
|
|
|
|
features available.
|
2016-10-25 21:40:30 +00:00
|
|
|
|
|
|
|
|
## Why do you use Docker?
|
|
|
|
|
|
2016-10-25 23:36:29 +00:00
|
|
|
Building fuzzers requires building your target with a fresh Clang compiler and special compiler flags.
|
2016-10-25 21:40:30 +00:00
|
|
|
An easy-to-use Docker image is provided to simplify toolchain distribution. This also limits our exposure
|
|
|
|
|
to multitude of Linux varieties and provides a reproducible and (more) secure environment for fuzzer
|
|
|
|
|
building and execution.
|
|
|
|
|
|
|
|
|
|
If you'd like to get more familiar with how libFuzzer-style fuzzers work in
|
|
|
|
|
general, check out [this page](http://llvm.org/docs/LibFuzzer.html).
|
