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

Link for bugs.chromium.org expires #12732

Open
n132 opened this issue Nov 18, 2024 · 2 comments
Open

Link for bugs.chromium.org expires #12732

n132 opened this issue Nov 18, 2024 · 2 comments

Comments

@n132
Copy link

n132 commented Nov 18, 2024

Links expire after using a new issue track website, for example, the following link is in the readme.md:

https://bugs.chromium.org/p/oss-fuzz/issues/list?q=Type%3DBug-Security%20label%3Aclusterfuzz%20-status%3ADuplicate%2CWontFix&can=1

But it redirects people to the new issue tracker which can't tell the correct number of vulnerabilities that OSS-Fuzz found.

A further request: Is it possible to link the new ID (new issue tracker) to the old ID?

For example: the old ID is 38900, when we visit crbug.com/oss-fuzz/38900 the site redirects us to https://issues.oss-fuzz.com/issues/42502089 but we can't find any information about 38900 in the new page. It's also great if you can tell the rules to map old ID to the new ID.

@n132
Copy link
Author

n132 commented Nov 18, 2024

In the new site (issue tracker of OSS-Fuzz), the following URL gives similar results:

https://issues.oss-fuzz.com/issues?q=type:vulnerability%20status:verified&p=1

However, when we want to list more than 2500 cases, it doesn't allow that. Some special API/method should be applied.

Any idea how to list all?

@n132
Copy link
Author

n132 commented Nov 18, 2024

By adding limits, such as those created before/after a date, I thought it would be able to list everything. But still asking for help if you have a better way/api.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant