Problems with oss-fuzz cluster on libpng (71681 and 71387)

[jbowler]

[To summarize briefly (it's fairly obvious):]

(https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=71681)

I don't know about the new fuzzing support but the commit message is fairly clear;

pnggroup/libpng@b7276ec

More details from the maintainer I assume, but I suggest direct communication. I don't have any access to that repo (it's probably private.)

Then: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=71387

You are also sending messages to an email without telling me what email you used, I thought it was [email protected] but I tried accessing the reports for Issue 71387 and was completely unable to get anywhere, I even created a gmail account to try to access them ([email protected], I figured that was more acceptable than the one they're using.)

[ctruta]

My bad: I should have known better: I should have deleted contrib/oss-fuzz/ after publishing the brand new and especially shiny pngfuzz repo. My original plan was to actually publish that repo, immediately after the deletion... but...

I keep my fingers crossed that I'll be able to do it tomorrow 🤞 after the announcement of the brand new and especially shiny libpng branch.

[ctruta]

I keep my fingers crossed that I'll be able to do it tomorrow 🤞 after the announcement of the brand new and especially shiny libpng branch.

As it turned out: no.

So I reverted both commits that I had applied since libpng-1.6.43. See pnggroup/libpng@cd5e582 and pnggroup/libpng@529e69e

@jbowler you may close this issue.