manunio

> I probably shouldn't have merged it because there's no one upstream to accept bug reports, but there's a linked issue where upstream agreed to the integration. Here there is...

Relevant discussion: [Integration with oss-fuzz fuzzing service #2371](https://github.com/encode/httpx/discussions/2371)

> That library is unmaintained/abandoned, so I don't know that fuzzing would be any use. Supposing it turns up anything, fixes would not be accepted. Hi, thanks for update, i...

> > That library is unmaintained/abandoned, so I don't know that fuzzing would be any use. Supposing it turns up anything, fixes would not be accepted. > ~~Hi, thanks for...

> Hi @manunio! Thanks for working on this. Looking at [google/oss-fuzz#8373](https://github.com/google/oss-fuzz/pull/8373), it appears your fuzz target fetches an arbitrary URL with arbitrary headers. My understanding is that a good fuzz...

@jsha friendly ping :) > If you decide to pursue this further, I'm happy to provide an email. That was my aim, i do wish to pursue it further with...

@marcusklaas Friendly Ping :)

> The Gmail account may be a problem, how it is exactly used for authentication? A Gmail/Google Id is required to access both Google's [issue tracker](https://bugs.chromium.org/p/oss-fuzz/issues/list) and the oss-fuzz [web...

> I have created the following Google account for the project: [email protected]. > > Which would be the next steps? > > Thanks. The next step would be creating a...

> OK, then please create it. > > Thanks. Hey, just an update. I'm working on the integration side but facing some issues with the oss-fuzz. I'll update you once...