-
Notifications
You must be signed in to change notification settings - Fork 187
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
Disable automatic OSS-Fuzz -> OSV import for BoringSSL #2178
Comments
oliverchang
added a commit
that referenced
this issue
May 12, 2024
Fixes #2178. BoringSSL maintainers would like more control / vetting of entries. Disable the import for now until we have a better system in place to enable that.
oliverchang
added a commit
that referenced
this issue
May 13, 2024
Fixes #2178. BoringSSL maintainers would like more control / vetting of entries. Disable the import for now until we have a better system in place to enable that.
evverx
added a commit
to evverx/osv.dev
that referenced
this issue
May 17, 2024
It's a follow-up to google#2201. The comments point to google#2178 because the reason is the same.
evverx
added a commit
to evverx/osv.dev
that referenced
this issue
Sep 18, 2024
It's a follow-up to google#2201. The comments point to google#2178 because the reason is the same.
evverx
added a commit
to evverx/osv.dev
that referenced
this issue
Sep 20, 2024
It's a follow-up to google#2201. The comments point to google#2178 because the reason is the same.
oliverchang
pushed a commit
that referenced
this issue
Sep 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In principle, this import is great and we'd love to have it. However, until the following issues are resolved, the tradeoffs are not viable. I would much much rather we lose the OSV import than lose the fuzzers, so please disable the import.
The text was updated successfully, but these errors were encountered: