-
Notifications
You must be signed in to change notification settings - Fork 425
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
Missing security policy prevents a responsible disclosure in case a security vulnerability is discovered #1011
Comments
Hi folks, is there a problem in adding a security policy? |
@quapka thanks for bringing this up! Sorry for late reply, this is because all the maintainers have low bandwidth to dedicate to this project. We'll add the security policy closer to releasing 0.16 version. |
I see, @tyranron. When is the release expected or is there a secure communication channel in the meantime? Adding a security policy should not actually take much time. 🙂 |
I am personally a big fan of immediate public disclosure / radical transparency (I used to manage security updates for macOS and Firefox FWIW) but we haven't had a discussion between the maintainers about what we should do for juniper yet. |
@LegNeato that is a resume worth mentioning IMHO. It is the maintainers/code-owners decision how such issues should be handled. Simply coming as an outsider to a project it is nice to have the disclosure policy clear & explicit (say in |
Hello, who should I contact for security vulnerabilities with this organization? I tried messaging the owner of the crate, but he is currently serving in the Ukraine army and I want to make sure I contact the correct people. |
Is your feature request related to a problem? Please describe.
There is no security policy set up for this project. Also, searching for
security
in the documentation yields 0 results.Describe the solution you'd like
A security policy is set up, e.g. using GitHub Security Advisory. Also when creating a new issue there should be an option to report a security vulnerability that links to the policy.
Describe alternatives you've considered
One can look for/guess e-mails of trusted maintainers, but that is far from a good practice.
Additional context
None.
The text was updated successfully, but these errors were encountered: