Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CIFuzz (OSS-Fuzz in our CI) #79

Open
gilles-peskine-arm opened this issue Dec 6, 2022 · 0 comments
Open

CIFuzz (OSS-Fuzz in our CI) #79

gilles-peskine-arm opened this issue Dec 6, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@gilles-peskine-arm
Copy link
Contributor

The OSS-Fuzz project runs various fuzzers (including the mbedtls fuzzer) on their own infrastructure continuously, updating the dependencies every few days. In addition, they provide CIFuzz, which allows running one OSS-Fuzz project on a specified commit. CIFuzz runs in GitHub actions.

Goals of this task:

  • Set up what it takes to run CIFuzz for the mbedtls fuzzer manually on one commit.
  • Document how to run the mbedtls fuzzer manually.
  • Determine whether the code coverage measurement allows fuzzing to be skipped when a feature is not affected.

Follow-ups:

  • Estimate how much enabling CIFuzz in pull requests would cost us in terms of GitHub action budget. If acceptable, enable CIFuzz in our pull request CI.
  • Possibly, study how we could extend our CIFuzz integration to also run fuzzers that have mbedtls as a subproject (bignum-fuzzer, ecc-diff-fuzzer, cryptofuzz).
@gilles-peskine-arm gilles-peskine-arm added the enhancement New feature or request label Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant