-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Security Policies #430
Comments
Here is what I provided to the Node.js project in the past based on other policies and structure that I thought was well thought through. Specifically the ember security process which has links to other great sources. Welcome comments on any of it. Important aspects are the communication with the disclosing party (read 1337 haxor) and then with the public once a patch is in place. I simply can't stress good communication enough. So a clear channel to get security issues on and a good output channel to broadcast them once addressed. The other important thing is what happens in the middle. Obviously communication as to what is going on with a fix, but timely fixes as well. Pretty sure that is already engrained in the spirit of io.js based on the wanting to get latest v8 in quickly and release quickly, so not that worried about being able to execute on that. Reporting a BugAll security bugs in io.js are taken seriously and should be reported by email to security@iojs.org. This will be delivered to a subset of the core team who handle security issues. Your email will be acknowledged within 24 hours, and you’ll receive a more detailed response to your email within 48 hours indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement, and may ask for additional information or guidance surrounding the reported issue. These updates will be sent at least every five days, in practice, this is more likely to be every 24-48 hours. If you have not received a reply to your email within 48 hours, or have not heard from the security team for the past five days, there are a few steps you can take:
Security bugs in third party modules should be reported to their respective maintainers and can also be coordinated through the Node Security Project. Thank you for improving the security of Node.js. Your efforts and responsible disclosure are greatly appreciated and will be acknowledged. Disclosure PolicyHere is the security disclosure policy for Node.js
Receiving Security UpdatesSecurity notifications will be distributed via the following methods.
Core Security TeamThe following people make up the io.js core security team.
Comments on this PolicyIf you have suggestions on how this process could be improved please submit a pull request or email security@iojs.org to discuss. |
Seems like the structure put forward by @evilpacket is uncontested. Would a |
yes please! :) |
@evilpacket would you like to send in a PR with your policy? |
Yes. I'll hit that up after node summit.
|
@evilpacket poke! it's after Node Summit :) |
@evilpacket Status? |
This initial draft was collaboratively authored by @mikeal and @jasnell via a shared google doc on 2015-04-02/2015-04-03. The initial text was provided by @mikeal based on current io.js documented practice with editorial, structural and content details added by @jasnell. The initial proposal for repository consolidation was authored initially by @jasnell.
ping @evilpacket, I can PR this in if you'd like. |
Is anything happening with this? We have some security process in-place, and a note in the readme. Do we still want this more detailed document? |
No movment here since a long time, and some information above is already outdated with the node merger. I'll close this. |
We should have well documented policies around vulnerability disclosure, reporting and security advisory notices.
I bet @evilpacket has things to say :)
The text was updated successfully, but these errors were encountered: