From ed1fbf17adbbe9e0f8ba603b3e986a8017660401 Mon Sep 17 00:00:00 2001 From: Rod Vagg Date: Wed, 1 Feb 2017 23:42:33 +1100 Subject: [PATCH] Blog: Update January OpenSSL post with releases PR-URL: https://github.com/nodejs/nodejs.org/pull/1120 --- .../blog/vulnerability/openssl-january-2017.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/locale/en/blog/vulnerability/openssl-january-2017.md b/locale/en/blog/vulnerability/openssl-january-2017.md index 5e144b87c677a..872bac4f9ccc0 100644 --- a/locale/en/blog/vulnerability/openssl-january-2017.md +++ b/locale/en/blog/vulnerability/openssl-january-2017.md @@ -7,6 +7,22 @@ layout: blog-post.hbs author: Rod Vagg --- +## _(Update 1-February-2017)_ Releases available + +Updates are now available for all active Node.js release lines. + +The following releases are bundled with OpenSSL 1.0.2k: + +* [Node.js 7.5.0 (Current)](https://nodejs.org/en/blog/release/v7.5.0/) +* [Node.js 6.9.5 (LTS "Boron")](https://nodejs.org/en/blog/release/v6.9.5/) +* [Node.js 4.7.3 (LTS "Argon")](https://nodejs.org/en/blog/release/v4.7.3/) + +While this is not a critical update, all users of these release lines should upgrade at their earliest convenience. + +***Original post is included below*** + +-------------------------------------- + The OpenSSL project has [announced](https://mta.openssl.org/pipermail/openssl-announce/2017-January/000092.html) the immediate availability of OpenSSL version 1.0.2k. Although the OpenSSL team have determined a maximum severity rating of "moderate", the Node.js crypto team (Ben Noordhuis, Shigeki Ohtsu and Fedor Indutny) have determined the impact to Node users is "low". Details on this determination can be found below.