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

Create a Security Policy #3356

Closed
wants to merge 1 commit into from
Closed

Conversation

joycebrum
Copy link
Contributor

Closes #3355

I’ve created the SECURITY.md file considering the report vulnerability through security advisory, which is a new github feature still in beta and that has to be enabled.

If you rather not enabling it there is also the possibility to receive the vulnerability report through an email, in this case just let me know which email it would be and I’ll submit the change.

Besides that feel free to edit or suggest any changes to this document, it is supposed to reflect the amount of effort the team can offer to handle vulnerabilities.

@vitaut
Copy link
Contributor

vitaut commented Mar 18, 2023

Thanks for the PR. Considering that we have limited resources, everything is a best effort. We will still prioritize security-related issues but I'd rather not create any expectations that we cannot meet. I enabled private vulnerability reporting which I think is sufficient for now.

@vitaut vitaut closed this Mar 18, 2023
@vitaut vitaut mentioned this pull request Mar 18, 2023
@joycebrum
Copy link
Contributor Author

joycebrum commented Mar 20, 2023

@vitaut I've updated the document to be a best effort bases (https://github.com/joycebrum/fmt/blob/master-1/SECURITY.md). The Security Policy file is more about explaining the user what they should do when finding a vulnerability and what they should expect. Since the expectation is best effort bases, there is no problem to disclose it on the SECURITY.md (this is actually very common among open sources).

@vitaut
Copy link
Contributor

vitaut commented Mar 25, 2023

This looks reasonable but I don't think we need a top-level file for this. I suggest adding a section to the readme.

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

Successfully merging this pull request may close these issues.

Create a Security Policy
2 participants