[Security] Bump sshpk from 1.13.1 to 1.16.1 #29
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.
Bumps sshpk from 1.13.1 to 1.16.1. This update includes security fixes.
Vulnerabilities fixed
Sourced from The npm Advisory Database.
Sourced from The GitHub Security Advisory Database.
Sourced from The Node Security Working Group.
Release notes
Sourced from sshpk's releases.
Commits
1aece0d
certs should generate GeneralizedTime values for dates >2050 TritonDataCenter/node-sshpk#60 certs should generate GeneralizedTime values for dates >...684dbe6
handle pkcs8 ECDSA keys with missing public parts TritonDataCenter/node-sshpk#62 handle pkcs8 ECDSA keys with missing public parts574ff21
support for PKCS8 encrypted private keys TritonDataCenter/node-sshpk#18 support for PKCS8 encrypted private keysf647cf2
Add support for PuTTY PPK format TritonDataCenter/node-sshpk#27 Add support for PuTTY PPK format44aec4a
want support for SPKI fingerprint format TritonDataCenter/node-sshpk#59 want support for SPKI fingerprint format385ff11
wish: add support for x509 certificates in text form TritonDataCenter/node-sshpk#48 wish: add support for x509 certificates in text formc7a6c68
des-ede3-cbc encrypted keys broken TritonDataCenter/node-sshpk#58 des-ede3-cbc encrypted keys broken2ab4f2a
md5 fingerprints not quite right TritonDataCenter/node-sshpk#56 md5 fingerprints not quite right026ef47
stop using optional deps to fix webpack TritonDataCenter/node-sshpk#53 stop using optional deps to fix webpack53e23fe
Support PKCS#5 AES-256-CBC encrypted private keys TritonDataCenter/node-sshpk#50 Support PKCS#5 AES-256-CBC encrypted private keysDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot will not automatically merge this PR because it includes a minor update to a production dependency.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge@dependabot reopen
will reopen this PR if it is closed@dependabot ignore this [patch|minor|major] version
will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabot dashboard:
Finally, you can contact us by mentioning @dependabot.