OSS Fuzz issues contain broken link, discouraging contributions

[BenWiederhake]

It seems that google/oss-fuzz#13394 wasn't enough, since I still can't access the OSS Fuzz reports.

Example:
#8953
Gives me:

I don't really know how to fix this :(

[naoNao89]

This is OSS-Fuzz's intentional security design, not a bug. The tracker requires auth to protect sensitive vulnerability details. Major projects (Kubernetes, NGINX, curl) work within this model. Public alternatives: GitHub issues, Fuzz Introspector reports, and OSV.dev after 90-day disclosure. This is by-design, not fixable.

[BenWiederhake]

There seems to be a misunderstanding: As far as I understand, the uutils maintainers want these issues to be public. Therefore, this deviant behavior is an issue.

Now that I take a closer look, I've noticed that the issues are public, but one must click the second link, because the first doesn't work:

Also note that this issue is still ongoing. Example:

• Github issue: OSS-Fuzz issue 459369402 #9218 (public, but only contains a link)
• First linked issue: https://oss-fuzz.com/testcase?key=6497768795602944 (not visible, "You are not authorized to access this page!")
• Second linked issue: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=459369402 (forwards to:)
• (from second link) https://issues.oss-fuzz.com/issues/459369402 (public, contains all data including reproducer, hooray!)

That's still somewhat unexpected, so I consider this an issue. I'll update the issue title accordingly.