2017-01-31, Version 4.7.3 'Argon' (LTS) - #11083
Merged
MylesBorins merged 1 commit intoFeb 1, 2017
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
MylesBorins
force-pushed
the
v4.7.3-proposal
branch
from
52f7c12 to
ddea415
Compare
January 31, 2017 16:22
Copy link
Copy Markdown
Contributor
Author
|
CI: https://ci.nodejs.org/job/node-test-pull-request/6123/ |
Sorry, something went wrong.
jasnell
approved these changes
Jan 31, 2017
santigimeno
reviewed
Jan 31, 2017
Comment thread
CHANGELOG.md
Outdated
|
|
||
| ## 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 |
Copy link
Copy Markdown
Member
There was a problem hiding this comment.
s/Boron/Argon ?
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
There was a problem hiding this comment.
good catch!
Sorry, something went wrong.
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
MylesBorins
force-pushed
the
v4.7.3-proposal
branch
from
ddea415 to
79f015a
Compare
January 31, 2017 18:28
Copy link
Copy Markdown
Contributor
Author
|
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 |
Sorry, something went wrong.
Copy link
Copy Markdown
Contributor
Author
|
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 |
Sorry, something went wrong.
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
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