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 #361

Merged
merged 1 commit into from
May 20, 2023
Merged

Create a Security Policy #361

merged 1 commit into from
May 20, 2023

Conversation

joycebrum
Copy link
Contributor

@joycebrum joycebrum commented May 17, 2023

Closes #360

I've created the SECURITY.md file considering the report vulnerability through security advisory, which is a new github feature.

If you're interested in GitHub's feature, it must be activated for the repository:

  1. Open the repo's settings
  2. Click on Code security & analysis
  3. Click "Enable" for "Private vulnerability reporting"

If you rather not enable 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.


The Security Policy can be seen either in the security page (https://github.com/joycebrum/getrandom/security) or in the about section of the github homepage:

image

Signed-off-by: Joyce <joycebrum@google.com>
@newpavlov
Copy link
Member

Thank you!

The CI failure is not relevant to this PR, so I will merge it.

@newpavlov newpavlov merged commit 5aa4105 into rust-random:master May 20, 2023
@joycebrum
Copy link
Contributor Author

joycebrum commented May 22, 2023

Hi @newpavlov, I'd like just to remind you to activate the security report through GitHub, otherwise the link won't work for the users:

  1. Open the repo's settings
  2. Click on Code security & analysis
  3. Click "Enable" for "Private vulnerability reporting"

Thanks! 😄


If you have discovered a security vulnerability in this project, please report it privately. **Do not disclose it as a public issue.** This gives us time to work with you to fix the issue before public exposure, reducing the chance that the exploit will be used before a patch is released.

Please disclose it at [security advisory](https://github.com/rust-random/getrandom/security/advisories/new).
Copy link

@SimenB SimenB Jun 5, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this 404s, fwiw (mostly a ping, I guess 😀 #361 (comment))

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for reporting it! Fixed.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woah, quick! 😀

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
3 participants