Add protocol to IPFS/IPNS hash #48
Assignees
Comments
fmiras
pushed a commit
that referenced
this issue
Dec 26, 2018
Bumps [sshpk](https://github.com/joyent/node-sshpk) from 1.13.1 to 1.16.0. **This update includes security fixes.** <details> <summary>Vulnerabilities fixed</summary> *Sourced from [The npm Advisory Database](https://npmjs.com/advisories/606).* > **Regular Expression Denial of Service** > Versions of `sshpk` before 1.13.2 or 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys. > > Affected versions: <1.13.2; >=1.14.0 <1.14.1 *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](https://github.com/nodejs/security-wg/blob/master/vuln/npm/401.json).* > **Denial of Service** > `sshpk` is vulnerable to ReDoS when parsing crafted invalid public keys > > Affected versions: <=1.13.1 </details> <details> <summary>Release notes</summary> *Sourced from [sshpk's releases](https://github.com/joyent/node-sshpk/releases).* > ## 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](https://github-redirect.dependabot.com/joyent/node-sshpk/issues/48) > > ## v1.15.2 > * New API for accessing x509 extensions in certificates > * Fixes for [#52](https://github-redirect.dependabot.com/joyent/node-sshpk/issues/52), [#50](https://github-redirect.dependabot.com/joyent/node-sshpk/issues/50) > > ## 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 </details> <details> <summary>Commits</summary> - [`574ff21`](TritonDataCenter/node-sshpk@574ff21) TritonDataCenter/node-sshpk#18 support for PKCS8 encrypted private keys - [`f647cf2`](TritonDataCenter/node-sshpk@f647cf2) TritonDataCenter/node-sshpk#27 Add support for PuTTY PPK format - [`44aec4a`](TritonDataCenter/node-sshpk@44aec4a) TritonDataCenter/node-sshpk#59 want support for SPKI fingerprint format - [`385ff11`](TritonDataCenter/node-sshpk@385ff11) TritonDataCenter/node-sshpk#48 wish: add support for x509 certificates in text form - [`c7a6c68`](TritonDataCenter/node-sshpk@c7a6c68) TritonDataCenter/node-sshpk#58 des-ede3-cbc encrypted keys broken - [`2ab4f2a`](TritonDataCenter/node-sshpk@2ab4f2a) TritonDataCenter/node-sshpk#56 md5 fingerprints not quite right - [`026ef47`](TritonDataCenter/node-sshpk@026ef47) TritonDataCenter/node-sshpk#53 stop using optional deps to fix webpack - [`53e23fe`](TritonDataCenter/node-sshpk@53e23fe) TritonDataCenter/node-sshpk#50 Support PKCS#5 AES-256-CBC encrypted private keys - [`6b68d49`](TritonDataCenter/node-sshpk@6b68d49) TritonDataCenter/node-sshpk#54 want API for accessing x509 extensions - [`1088992`](TritonDataCenter/node-sshpk@1088992) TritonDataCenter/node-sshpk#52 Buffer no longer performs length check for hex strings i... - Additional commits viewable in [compare view](TritonDataCenter/node-sshpk@v1.13.1...v1.16.0) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=sshpk&package-manager=npm_and_yarn&previous-version=1.13.1&new-version=1.16.0) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - 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. </details>
fmiras
pushed a commit
that referenced
this issue
Jan 24, 2019
Bumps [sshpk](https://github.com/joyent/node-sshpk) from 1.13.1 to 1.16.1. **This update includes security fixes.** <details> <summary>Vulnerabilities fixed</summary> *Sourced from [The npm Advisory Database](https://npmjs.com/advisories/606).* > **Regular Expression Denial of Service** > Versions of `sshpk` before 1.13.2 or 1.14.1 are vulnerable to regular expression denial of service when parsing crafted invalid public keys. > > Affected versions: <1.13.2; >=1.14.0 <1.14.1 *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](https://github.com/nodejs/security-wg/blob/master/vuln/npm/401.json).* > **Denial of Service** > `sshpk` is vulnerable to ReDoS when parsing crafted invalid public keys > > Affected versions: <=1.13.1 </details> <details> <summary>Release notes</summary> *Sourced from [sshpk's releases](https://github.com/joyent/node-sshpk/releases).* > ## 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](https://github-redirect.dependabot.com/joyent/node-sshpk/issues/48) > > ## v1.15.2 > * New API for accessing x509 extensions in certificates > * Fixes for [#52](https://github-redirect.dependabot.com/joyent/node-sshpk/issues/52), [#50](https://github-redirect.dependabot.com/joyent/node-sshpk/issues/50) > > ## 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 </details> <details> <summary>Commits</summary> - [`1aece0d`](TritonDataCenter/node-sshpk@1aece0d) TritonDataCenter/node-sshpk#60 certs should generate GeneralizedTime values for dates >... - [`684dbe6`](TritonDataCenter/node-sshpk@684dbe6) TritonDataCenter/node-sshpk#62 handle pkcs8 ECDSA keys with missing public parts - [`574ff21`](TritonDataCenter/node-sshpk@574ff21) TritonDataCenter/node-sshpk#18 support for PKCS8 encrypted private keys - [`f647cf2`](TritonDataCenter/node-sshpk@f647cf2) TritonDataCenter/node-sshpk#27 Add support for PuTTY PPK format - [`44aec4a`](TritonDataCenter/node-sshpk@44aec4a) TritonDataCenter/node-sshpk#59 want support for SPKI fingerprint format - [`385ff11`](TritonDataCenter/node-sshpk@385ff11) TritonDataCenter/node-sshpk#48 wish: add support for x509 certificates in text form - [`c7a6c68`](TritonDataCenter/node-sshpk@c7a6c68) TritonDataCenter/node-sshpk#58 des-ede3-cbc encrypted keys broken - [`2ab4f2a`](TritonDataCenter/node-sshpk@2ab4f2a) TritonDataCenter/node-sshpk#56 md5 fingerprints not quite right - [`026ef47`](TritonDataCenter/node-sshpk@026ef47) TritonDataCenter/node-sshpk#53 stop using optional deps to fix webpack - [`53e23fe`](TritonDataCenter/node-sshpk@53e23fe) TritonDataCenter/node-sshpk#50 Support PKCS#5 AES-256-CBC encrypted private keys - Additional commits viewable in [compare view](TritonDataCenter/node-sshpk@v1.13.1...v1.16.1) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=sshpk&package-manager=npm_and_yarn&previous-version=1.13.1&new-version=1.16.1) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - 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. </details>
fmiras
pushed a commit
that referenced
this issue
Feb 8, 2019
Bumps [extend](https://github.com/justmoon/node-extend) from 3.0.1 to 3.0.2. **This update includes security fixes.** <details> <summary>Vulnerabilities fixed</summary> *Sourced from The GitHub Security Advisory Database.* > **Low severity vulnerability that affects extend** > A prototype pollution vulnerability was found in module extend <2.0.2, ~<3.0.2 that allows an attacker to inject arbitrary properties onto Object.prototype. > > Affected versions: >= 3.0.0 < 3.0.2 </details> <details> <summary>Changelog</summary> *Sourced from [extend's changelog](https://github.com/justmoon/node-extend/blob/master/CHANGELOG.md).* > 3.0.2 / 2018-07-19 > ================== > * [Fix] Prevent merging `__proto__` property ([#48](https://github-redirect.dependabot.com/justmoon/node-extend/issues/48)) > * [Dev Deps] update `eslint`, `@ljharb/eslint-config`, `tape` > * [Tests] up to `node` `v10.7`, `v9.11`, `v8.11`, `v7.10`, `v6.14`, `v4.9`; use `nvm install-latest-npm` </details> <details> <summary>Commits</summary> - [`8d106d2`](justmoon/node-extend@8d106d2) v3.0.2 - [`e97091f`](justmoon/node-extend@e97091f) [Dev Deps] update `tape` - [`e841aac`](justmoon/node-extend@e841aac) [Tests] up to `node` `v10.7` - [`0e68e71`](justmoon/node-extend@0e68e71) [Fix] Prevent merging __proto__ property - [`a689700`](justmoon/node-extend@a689700) Only apps should have lockfiles - [`f13c1c4`](justmoon/node-extend@f13c1c4) [Dev Deps] update `eslint`, `@ljharb/eslint-config`, `tape` - [`f3570fe`](justmoon/node-extend@f3570fe) [Tests] up to `node` `v10.0`, `v9.11`, `v8.11`, `v7.10`, `v6.14`, `v4.9`; use... - See full diff in [compare view](justmoon/node-extend@v3.0.1...v3.0.2) </details> <br /> [](https://dependabot.com/compatibility-score.html?dependency-name=extend&package-manager=npm_and_yarn&previous-version=3.0.1&new-version=3.0.2) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - 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. </details>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When storing the metadata format in the LANDRegistry, add the protocol in front of the IPFS hash for the client to know what type of gateway to use.
Example:
0,,,ipns:QmVP3WAkJRcc9AkS83r5fwaWAxpgtP7cpDupVWRos9qStY
0,,,ipfs:QmVP3WAkJRcc9AkS83r5fwaWAxpgtP7cpDupVWRos9qStY
The text was updated successfully, but these errors were encountered: