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

Continuous fuzzing #496

Open
ia0 opened this issue May 29, 2024 · 0 comments
Open

Continuous fuzzing #496

ia0 opened this issue May 29, 2024 · 0 comments
Labels
for:maintainability Improves maintainers life for:security Improves firmware or project security good first issue Good for newcomers needs:implementation Needs implementation to complete

Comments

@ia0
Copy link
Member

ia0 commented May 29, 2024

We could have simple continuous fuzzing by leveraging scheduled workflow and caches. Every week, we run all fuzz targets for 10 minutes each and cache their corpus. Next week, we repeat starting from the cached corpus.

There should be a ci-fuzz action that loads the cache and runs regression testing (i.e. just runs on the corpus). This action should have an equivalent ./scripts/ci-fuzz.sh script.

@ia0 ia0 added needs:implementation Needs implementation to complete for:security Improves firmware or project security for:maintainability Improves maintainers life labels May 29, 2024
@ia0 ia0 added the good first issue Good for newcomers label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for:maintainability Improves maintainers life for:security Improves firmware or project security good first issue Good for newcomers needs:implementation Needs implementation to complete
Projects
None yet
Development

No branches or pull requests

1 participant