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

Integration into OSS-fuzz #165

Closed
DavidKorczynski opened this issue Feb 12, 2021 · 2 comments
Closed

Integration into OSS-fuzz #165

DavidKorczynski opened this issue Feb 12, 2021 · 2 comments

Comments

@DavidKorczynski
Copy link
Contributor

Hi Maintainers,

I have worked a bit on setting fuzzing up for w3m by way of OSS-Fuzz. Essentially, OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects, and it would be great to have w3m integrated. The only expectation of integrating into OSS-Fuzz is that bugs will be fixed. This is not a "hard" requirement in that no one enforces this and the main point is if bugs are not fixed then it is a waste of resources to run the fuzzers, which we would like to avoid.

In this PR google/oss-fuzz#5127 I have done exactly that, namely created the necessary logic from an OSS-Fuzz perspective to integrate w3m. If you would like to integrate, could you please provide a set of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. The emails should be linked to a Google account in order to view the detailed reports and notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.

At the moment I stored the fuzzers in the Google OSS-Fuzz repository, but we can move them up here to make maintenance easier.

@tats
Copy link
Owner

tats commented Feb 24, 2021

Please use my email addresss tats@debian.org to send reports.

@tats
Copy link
Owner

tats commented Mar 3, 2021

It's now working. Thank you.

@tats tats closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants