starred/hickory-dns

Fork 0

mirror of https://github.com/hickory-dns/hickory-dns.git synced 2026-04-25 11:15:54 +03:00

[GH-ISSUE #1790] Integration with oss-fuzz fuzzing service #769

New issue

Closed

opened 2026-03-16 00:10:38 +03:00 by kerem · 6 comments

kerem commented

2026-03-16 00:10:38 +03:00

Owner

Originally created by @manunio on GitHub (Oct 8, 2022).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1790

Hi, I would like to help integrate this project into OSS-Fuzz.

As an initial step for integration I have created this PR: https://github.com/google/oss-fuzz/pull/8711, it contains necessary logic from an OSS-Fuzz perspective to integrate trust-dns.
OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects.
As trust-dns already have cargo-fuzz based fuzzing implemented, this makes it easily compatible with oss-fuzz out of box.
If you would like to integrate, the only thing I need is a list of email(s), it must be associated with a google account like
gmail (why?). by doing that, the provided email(s) will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats.
As an alternative, if you don't have a google/gmail id, but still wish to integrate. I can add my mail id for time being and monitor bug/crashes.
Notice the email(s) affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.

Originally created by @manunio on GitHub (Oct 8, 2022). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1790 Hi, I would like to help integrate this project into [OSS-Fuzz](https://github.com/google/oss-fuzz). - As an initial step for integration I have created this PR: https://github.com/google/oss-fuzz/pull/8711, it contains necessary logic from an OSS-Fuzz perspective to integrate trust-dns. - OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects. - As trust-dns already have cargo-fuzz based fuzzing implemented, this makes it easily compatible with oss-fuzz out of box. - If you would like to integrate, the only thing I need is a list of email(s), it must be associated with a google account like gmail ([why?](https://google.github.io/oss-fuzz/faq/#why-do-you-require-a-google-account-for-authentication)). by doing that, the provided email(s) will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. - As an alternative, if you don't have a google/gmail id, but still wish to integrate. I can add my mail id for time being and monitor bug/crashes. - Notice the email(s) affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.

kerem closed this issue

2026-03-16 00:10:43 +03:00

kerem commented

2026-03-16 00:10:49 +03:00

Author

Owner

@bluejekyll commented on GitHub (Oct 8, 2022):

Is there an option to have oss-fuzz open Issues directly with the project with the reports you mention, rather than email?

@bluejekyll commented on GitHub (Oct 8, 2022): Is there an option to have oss-fuzz open Issues directly with the project with the reports you mention, rather than email?

kerem commented

2026-03-16 00:10:54 +03:00

Author

Owner

@manunio commented on GitHub (Oct 8, 2022):

Is there an option to have oss-fuzz open Issues directly with the project with the reports you mention, rather than email?

Hi, There is an option which allows filling report as github issue, but it just points to monorail issue tracker or ossfuzz.com, where you can see full details of your report, but it still needs email(google account) for access.

From FAQ: why-do-you-use-a-different-issue-tracker-for-reporting-bugs-in-oss-projects:

Security access control is important for the kind of issues that OSS-Fuzz detects. We will reconsider the GitHub issue tracker once the access control feature is available.

@manunio commented on GitHub (Oct 8, 2022): > Is there an option to have oss-fuzz open Issues directly with the project with the reports you mention, rather than email? Hi, There is an option which allows filling report as github issue, but it just points to monorail issue tracker or ossfuzz.com, where you can see full details of your report, but it still needs email(google account) for access. [From FAQ: why-do-you-use-a-different-issue-tracker-for-reporting-bugs-in-oss-projects](https://google.github.io/oss-fuzz/faq/#why-do-you-use-a-different-issue-tracker-for-reporting-bugs-in-oss-projects): > Security access control is important for the kind of issues that OSS-Fuzz detects. We will reconsider the GitHub issue tracker once the [access control feature](https://github.com/isaacs/github/issues/37) is available. >

kerem commented

2026-03-16 00:10:59 +03:00

Author

Owner

@manunio commented on GitHub (Oct 9, 2022):

@bluejekyll if you have any problem with email, I can report bug reports here for the time being.

@manunio commented on GitHub (Oct 9, 2022): @bluejekyll if you have any problem with email, I can report bug reports here for the time being.

kerem commented

2026-03-16 00:11:04 +03:00

Author

Owner

@bluejekyll commented on GitHub (Oct 9, 2022):

No, it should be fine. I have a Google email that can work. Thanks for putting this together!

bluejekyll at gmail will work.

@bluejekyll commented on GitHub (Oct 9, 2022): No, it should be fine. I have a Google email that can work. Thanks for putting this together! bluejekyll at gmail will work.

kerem commented

2026-03-16 00:11:09 +03:00

Author

Owner

@djc commented on GitHub (Oct 10, 2022):

@manunio can you also add me? I'm djc.ochtman at GMail.

FWIW @bluejekyll we also use this for rustls and the reporting infra is pretty easy to deal with.

@djc commented on GitHub (Oct 10, 2022): @manunio can you also add me? I'm djc.ochtman at GMail. FWIW @bluejekyll we also use this for rustls and the reporting infra is pretty easy to deal with.

kerem commented

2026-03-16 00:11:14 +03:00

Author

Owner

@manunio commented on GitHub (Oct 10, 2022):

Closing this now, as trust-dns has been integrated in oss-fuzz :)

@manunio commented on GitHub (Oct 10, 2022): Closing this now, as trust-dns has been integrated in oss-fuzz :)

kerem referenced this issue

2026-03-16 02:18:57 +03:00

[PR #769] [MERGED] Bump openssl from 0.10.22 to 0.10.23 #1667