Continuous fuzzing through OSS-fuzz
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- testing-qa
Research direction
Start by reviewing the OSS-Fuzz integration pull request linked in the issue and the remaining application requirements. Confirm the maintainer email needed for bug reports; the integration is done when OSS-Fuzz can run continuous fuzzing for Ignition with a maintainer contact configured.
Written by the indexing model from the issue text.
Description
Feature Request
Desired Feature
Continuous fuzzing
I have been working on setting up continuous fuzzing of ignition through OSS-fuzz here: https://github.com/google/oss-fuzz/pull/5368
For those unfamiliar: Fuzzing is a way of testing applications whereby pseudo-random data is passed to a program with the goal of finding bugs and vulnerabilities. It has been effective in finding bugs in many open source projects.
Google's OSS-fuzz project offers free CPU-power and infrastructure for critical open source projects to run their fuzzers continuously. I have written an article here about an example of why it is important to run your fuzzers continuously: https://adalogics.com/blog/the-importance-of-continuity-in-fuzzing-cve-2020-28362
All that is needed to finish the integration application of ignition is at least one maintainers email address for bug reports.
- Dominant language
- Go
- Stars
- 974
- Forks
- 296
- Avg merge
- 6d 14h
- Merged PRs (30d)
- 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from coreos/ignition
-
butane
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
-
butane
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
butane
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
butane
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
butane
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100