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

Update Security Policy #21

Labels
content Issues/pr concerning content

Comments

@mikeal
Copy link
Contributor

mikeal commented Aug 5, 2015

We now have the security policy on the front page of nodejs.org (once we're ready to deploy the new website).

If there are any changes to be made to this policy please update https://github.com/nodejs/new.nodejs.org/blob/master/locale/en/security.md

@rvagg
@nodejs/security
@evilpacket
@nodejs/tsc

@evilpacket
Copy link

This is super great! Thanks for letting us know.

On Aug 5, 2015, at 2:05 PM, Mikeal Rogers [email protected] wrote:

We now have the security policy on the front page of nodejs.org (once we're ready to deploy the new website).

If there are any changes to be made to this policy please update https://github.com/nodejs/new.nodejs.org/blob/master/locale/en/security.md

@rvagg
@nodejs/security
@evilpacket


Reply to this email directly or view it on GitHub.

@fhemberger fhemberger added the content Issues/pr concerning content label Aug 28, 2015
@fhemberger
Copy link
Contributor

Add notice, which legacy versions of Node.js receive security fixes, see:
#74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment