You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been working on setting up continuous fuzzing of go-systemd through OSS-fuzz here: google/oss-fuzz#5231
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 go-systemd is at least one maintainers email address for bug reports.
The text was updated successfully, but these errors were encountered:
I have been working on setting up continuous fuzzing of go-systemd through OSS-fuzz here: google/oss-fuzz#5231
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 go-systemd is at least one maintainers email address for bug reports.
The text was updated successfully, but these errors were encountered: