-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Fuzzing sigstore #6890
Fuzzing sigstore #6890
Conversation
@oliverchang FYI... |
2265e46
to
654fe28
Compare
654fe28
to
3876686
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!
Included sigstore/sigstore project Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com>
3876686
to
2d73fd9
Compare
If we're fuzzing sigstore in OSS-Fuzz, then I think the PR adding ClusterFuzzLite to sigstore is wrong. |
OK, that Makes sense. I will remove the PR in sigstore to use the clusterfuzzlite. Thanks |
Yes. You can just use the instructions here to set up CIFuzz: https://google.github.io/oss-fuzz/getting-started/continuous-integration/ |
How do we coverage for oss-fuzz? Also for CIFuzz if there is crash will everyone be able to see the crash call-stack and the data that caused it to happen? |
Included sigstore/sigstore project