Fix sshpk version#80
Closed
iwko wants to merge 1 commit intoTritonDataCenter:masterfrom
iwko:bugfix/fix-sshpk-dependency-version
Closed
Fix sshpk version#80iwko wants to merge 1 commit intoTritonDataCenter:masterfrom iwko:bugfix/fix-sshpk-dependency-version
iwko wants to merge 1 commit intoTritonDataCenter:masterfrom
iwko:bugfix/fix-sshpk-dependency-version
Conversation
|
Any ETA to apply this fix? |
Author
|
Any ETA to apply this fix? |
Contributor
|
"Fix"? This patch locks sshpk to a version released in 2015 just to support Node.js 0.8.28 released in 2014? Seems like you're on your own for an edge case like this. |
|
👎 to this, sshpk < 1.13.2 has an identified vulnerability: https://hackerone.com/reports/319593 This change would cause any project using this lib even indirectly to get audit failures and vulnerability alerts. |
Merged
Contributor
|
Done as of PR #86 |
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
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.
This is fix for #79