Uh oh!
There was an error while loading. Please reload this page.
2017-01-31, Version 4.7.3 'Argon' (LTS) - #11083
Merged
Merged
Conversation
MylesBorinsforce-pushed
the
v4.7.3-proposal
branch
from
January 31, 2017 16:22
52f7c12 to
ddea415CompareMylesBorins
commented
Jan 31, 2017
ContributorAuthor
jasnell
approved these changes
Jan 31, 2017
| ## 2017-01-31, Version 4.7.3 'Argon' (LTS), @MylesBorins | ||
| This is a security release of the 'Boron' release line to upgrade OpenSSL to version 1.0.2k |
This is a security release of the 'Boron' release line to upgrade OpenSSL to 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 on the Nodejs.org website https://nodejs.org/en/blog/vulnerability/openssl-january-2017/ Notable Changes: * deps: - upgrade openssl sources to 1.0.2k (Shigeki Ohtsu) #11021 PR-URL: #11083
MylesBorinsforce-pushed
the
v4.7.3-proposal
branch
from
January 31, 2017 18:28
ddea415 to
79f015aCompareMylesBorins
commented
Jan 31, 2017
ContributorAuthor
One more go at CI: https://ci.nodejs.org/job/node-test-pull-request/6133/ the PR for the security update was all green, so I'll move ahead with the release either way after this run |
ContributorAuthor
Quick run of ws on v4.7.2 to see if ws failure is expected https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/553/ edit: failure is present on v4.7.2... moving forward with release |
MylesBorins added a commit
that referenced
this pull request
Feb 1, 2017
This is a security release of the 'Boron' release line to upgrade OpenSSL to 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 on the Nodejs.org website https://nodejs.org/en/blog/vulnerability/openssl-january-2017/ Notable Changes: * deps: - upgrade openssl sources to 1.0.2k (Shigeki Ohtsu) #11021 PR-URL: #11083
imyller added a commit
to imyller/meta-nodejs
that referenced
this pull request
Mar 2, 2017
This is a security release of the 'Boron' release line to upgrade OpenSSL to 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 on the Nodejs.org website https://nodejs.org/en/blog/vulnerability/openssl-january-2017/ Notable Changes: * deps: - upgrade openssl sources to 1.0.2k (Shigeki Ohtsu) nodejs/node#11021 PR-URL: nodejs/node#11083 Signed-off-by: Ilkka Myller <ilkka.myller@nodefield.com>
imyller added a commit
to imyller/meta-nodejs
that referenced
this pull request
Mar 2, 2017
This is a security release of the 'Boron' release line to upgrade OpenSSL to 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 on the Nodejs.org website https://nodejs.org/en/blog/vulnerability/openssl-january-2017/ Notable Changes: * deps: - upgrade openssl sources to 1.0.2k (Shigeki Ohtsu) nodejs/node#11021 PR-URL: nodejs/node#11083 Signed-off-by: Ilkka Myller <ilkka.myller@nodefield.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
2017-01-31, Version 4.7.3 'Argon' (LTS), @MylesBorins
This is a security release of the 'Boron' release line to upgrade OpenSSL to 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
on the Nodejs.org website.
Notable Changes
Commits
8029f64135] - deps: update openssl asm and asm_obsolete files (Shigeki Ohtsu) #110210081659a41] - deps: add -no_rand_screen to openssl s_client (Shigeki Ohtsu) nodejs/io.js#1836e55c3f4e21] - deps: fix asm build error of openssl in x86_win32 (Shigeki Ohtsu) iojs/io.js#138924640f9278] - deps: fix openssl assembly error on ia32 win32 (Fedor Indutny) iojs/io.js#13896c7bdf58e0] - deps: copy all openssl header files to include dir (Shigeki Ohtsu) #11021c80844769c] - deps: upgrade openssl sources to 1.0.2k (Shigeki Ohtsu) #11021e3915a415b] - openssl: fix keypress requirement in apps on win32 (Shigeki Ohtsu) iojs/io.js#1389