generated from ublue-os/base
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Write Runbooks for Addressing CVEs #554
Comments
dosubot
bot
added
the
stale
Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
label
Jul 10, 2024
dosubot
bot
removed
the
stale
Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
label
Jul 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When dealing with #553, I noticed we did not have a defined plan for dealing with CVEs. I think it would be valuable to have a runbook on how to address CVEs.
I think we should also include information in the contributing guide about how to responsibly disclose CVEs to the team.
Rough information that should go in the runbook: (thanks @bsherman)
The text was updated successfully, but these errors were encountered: