-
-
Notifications
You must be signed in to change notification settings - Fork 495
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] Updated the workflow and tried to simplify the OSS-fuzz and local fuzzing build. #168
Conversation
…ied to simplify the OSS-fuzz and local fuzzing build. Signed-off-by: Arjun <[email protected]>
Comment for Verification; |
Everything is working as expected https://github.com/google/oss-fuzz/actions/runs/8821238582 |
Hi @pkillarjun -- thanks for the contribution. I've thought about this further, and decided I don't have the time or knowledge to properly review OSS-Fuzz scripts and PRs. In addition, the |
Well, I never dreamed of this response and #169. |
I hope you are okay with these changes? |
I know it's not what you we're hoping for. But I appreciate you moving the oss-fuzz stuff to a fork. Those changes look reasonable to me! |
I understand your thoughts on forks, but OSS-Fuzz does not accept forks of some random dude on the internet, |
Hi @benhoyt, I am a maintainer of OSS-Fuzz. Just want to ensure that I understand the situation correctly : ) |
@DonggeLiu I don't mind if someone else uses the OSS-Fuzz service to fuzz inih, and I'm happy to receive real bug reports, but I'd rather not maintain the fuzz code and scripts anymore in my inih repo. |
Thanks for the confirmation, @benhoyt. |
ini_parse_string
fromini_parse
for better coverage and ease of use and understanding.libAFLDriver.a
library for libFuzzer targets.build.sh
from the official oss-fuzz repo and useoss-fuzz.sh
for compilation in the oss-fuzz infrastructure.Hey Benhoyt,
I will use this account to maintain all my OSS-Fuzz integrated projects.