-
Notifications
You must be signed in to change notification settings - Fork 44
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
A proposed security policy #376
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Language tweaks for clarity
Looks good to me. Depending on how you are able to deal with it I would consider to enable "private vulnerability reporting". If a security issue is public, everyone can read about them and abuse them until they are fixed. If they are private, they would have to find them out themself to abuse them, making it harder. I think in a project such as SolidOS this could be important, as I expect the time to a fix to be rather long (as it is largely volunteer-based). I guess, then the main question would be if it is easy for you to define an appropriate group of people that can read these issues (eg people who regularly contribute to the project). |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>
This should be a basis to start a security policy which can be than copied on all repositories we own.