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

Continuous fuzzing by way of Google's OSS-Fuzz #11100

Closed
DavidKorczynski opened this issue Aug 9, 2022 · 3 comments
Closed

Continuous fuzzing by way of Google's OSS-Fuzz #11100

DavidKorczynski opened this issue Aug 9, 2022 · 3 comments
Labels
api: cloudtasks Issues related to the Cloud Tasks API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@DavidKorczynski
Copy link

Hi,

I was wondering if you would like to integrate continuous fuzzing by way of OSS-Fuzz? Fuzzing is a way to automate test-case generation and has been heavily used for memory unsafe languages. Recently efforts have been put into fuzzing memory safe languages and Python is one of the languages where it would be great to use fuzzing.

In this google/oss-fuzz#8192 I did an initial integration into OSS-Fuzz. OSS-Fuzz is a free service run by Google that performs continuous fuzzing of important open source projects. Since this is also a Google project you should be able to reach out internally e.g. to the Google Open Source Security team (GOSST) if you have any questions.

If you would like to integrate, the only thing I need is a list of email(s) that will get access to the data produced by OSS-Fuzz, such as bug reports, coverage reports and more stats. Notice the emails affiliated with the project will be public in the OSS-Fuzz repo, as they will be part of a configuration file.

@product-auto-label product-auto-label bot added the api: cloudtasks Issues related to the Cloud Tasks API. label Aug 9, 2022
@ace-n
Copy link
Contributor

ace-n commented Aug 18, 2022

Hi @DavidKorczynski,

Thanks for the idea. Can you point to any bugs or previous security issues with this repo where this would have helped?

(We unfortunately don't have time to "implement fuzzing for fuzzing's sake", per se.)

@rogerthatdev rogerthatdev self-assigned this Aug 23, 2022
@rogerthatdev rogerthatdev added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Aug 23, 2022
@rogerthatdev rogerthatdev removed their assignment Aug 23, 2022
@parthea
Copy link
Contributor

parthea commented Apr 18, 2023

I'm going to transfer this issue to the google-cloud-python repository as we are preparing to move the code for google-cloud-tasks to that repository in the next 1-2 weeks.

@parthea parthea transferred this issue from googleapis/python-tasks Apr 18, 2023
@parthea
Copy link
Contributor

parthea commented Aug 14, 2023

Closing as duplicate of #11069

@parthea parthea closed this as completed Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: cloudtasks Issues related to the Cloud Tasks API. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

4 participants