[Security] Bump sshpk from 1.13.1 to 1.16.1
Bumps sshpk from 1.13.1 to 1.16.1. This update includes security fixes.
Vulnerabilities fixed
Sourced from The GitHub Security Advisory Database.
Moderate severity vulnerability that affects sshpk The sshpk NPM package is vulnerable to ReDoS when parsing crafted invalid public keys.
Affected versions: < 1.13.2
Sourced from The Node Security Working Group.
Denial of Service
sshpkis vulnerable to ReDoS when parsing crafted invalid public keysAffected versions: <=1.13.1
Release notes
Sourced from sshpk's releases.
v1.16.1
- Fixes for #60 (correctly encoding certificates with expiry dates >=2050), #62 (accepting PKCS#8 EC private keys with missing public key parts)
v1.16.0
- Add support for SPKI fingerprints, PuTTY PPK format (public-key only for now), PKCS#8 PBKDF2 encrypted private keys
- Fix for #48
v1.15.2
v1.14.1
- Remove all remaining usage of jodid25519 (abandoned dep)
- Add support for DNSSEC key format
- Add support for Ed25519 keys in PEM format (according to draft-curdle-pkix)
- Fixes for X.509 encoding issues (asn.1 NULLs in RSA certs, cert string type mangling)
- Performance issues parsing long SSH public keys
Commits
1aece0djoyent/node-sshpk#60 certs should generate GeneralizedTime values for dates >...684dbe6joyent/node-sshpk#62 handle pkcs8 ECDSA keys with missing public parts574ff21joyent/node-sshpk#18 support for PKCS8 encrypted private keysf647cf2joyent/node-sshpk#27 Add support for PuTTY PPK format44aec4ajoyent/node-sshpk#59 want support for SPKI fingerprint format385ff11joyent/node-sshpk#48 wish: add support for x509 certificates in text formc7a6c68joyent/node-sshpk#58 des-ede3-cbc encrypted keys broken2ab4f2ajoyent/node-sshpk#56 md5 fingerprints not quite right026ef47joyent/node-sshpk#53 stop using optional deps to fix webpack53e23fejoyent/node-sshpk#50 Support PKCS#5 AES-256-CBC encrypted private keys- Additional commits viewable in compare view
Dependabot 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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot badge mewill comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in the .dependabot/config.yml file in this repo:
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Might be related to #11202 actually, since it shows up in duckdb.sql
Can we perhaps ignore objects of type builtin_function_or_method in replacement scans entirely?