Chore(deps): bump node-forge from 1.0.0 to 1.1.0 #29

Merged
argoyle merged 1 commits from dependabot-npm_and_yarn-node-forge-1.1.0 into main 2022-01-08 14:45:08 +00:00
argoyle commented 2022-01-08 01:50:39 +00:00 (Migrated from gitlab.com)

Bumps node-forge from 1.0.0 to 1.1.0.

Changelog

Sourced from node-forge's changelog.

1.1.0 - 2022-01-06

Fixed

  • [x509]: Correctly compute certificate issuer and subject hashes to match behavior of openssl.
  • [pem]: Accept certificate requests with "NEW" in the label. "BEGIN NEW CERTIFICATE REQUEST" handled as "BEGIN CERTIFICATE REQUEST".
Commits
  • cb93fe5 Release 1.1.0.
  • c9d3cb7 Update changelog.
  • bbd80a4 Adjust how PEM CSR with "NEW" are handled.
  • e1e8762 Add pem unit tests for NEW in CSR labels.
  • 9c2aba1 Accept CSRs with NEW in the label for decoding.
  • fb9d7f1 Update changelog.
  • eca1527 Add test for issuer and subject hashes
  • cebb5ff FIX [x509] Certificate issuer and subject hash correctly computed
  • ea4a83c Start 1.0.1-0.
  • See full diff in compare view


Dependabot commands
You can trigger Dependabot actions by commenting on this MR
  • $dependabot rebase will rebase this MR
  • $dependabot recreate will recreate this MR rewriting all the manual changes and resolving conflicts
Bumps [node-forge](https://github.com/digitalbazaar/forge) from 1.0.0 to 1.1.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md">node-forge's changelog</a>.</em></p> <blockquote> <h2>1.1.0 - 2022-01-06</h2> <h3>Fixed</h3> <ul> <li>[x509]: Correctly compute certificate issuer and subject hashes to match behavior of openssl.</li> <li>[pem]: Accept certificate requests with &quot;NEW&quot; in the label. &quot;BEGIN NEW CERTIFICATE REQUEST&quot; handled as &quot;BEGIN CERTIFICATE REQUEST&quot;.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/digitalbazaar/forge/commit/cb93fe5ce2d6f9a4fd9aaca5067c2cfe887a24ca"><code>cb93fe5</code></a> Release 1.1.0.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/c9d3cb72cc97c5ac41a53348a0179f190135ae8e"><code>c9d3cb7</code></a> Update changelog.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/bbd80a40df7bc2d573b1e95ea7bde0fa194417c1"><code>bbd80a4</code></a> Adjust how PEM CSR with &quot;NEW&quot; are handled.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/e1e8762f085d0f6cd7ba216cf260cf31050d19f5"><code>e1e8762</code></a> Add pem unit tests for NEW in CSR labels.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/9c2aba10fd4af7799177c21f56363af696c629a5"><code>9c2aba1</code></a> Accept CSRs with NEW in the label for decoding.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/fb9d7f1e4e2b89f8abf01f0044906b0cc07eac92"><code>fb9d7f1</code></a> Update changelog.</li> <li><a href="https://github.com/digitalbazaar/forge/commit/eca152796ab05a639e7b03b23584953f93b7af74"><code>eca1527</code></a> Add test for issuer and subject hashes</li> <li><a href="https://github.com/digitalbazaar/forge/commit/cebb5ff18773610b4078193c864f028b4ab417e6"><code>cebb5ff</code></a> FIX [x509] Certificate issuer and subject hash correctly computed</li> <li><a href="https://github.com/digitalbazaar/forge/commit/ea4a83c9bb8cdc667623ff7ffc750a628f8d9181"><code>ea4a83c</code></a> Start 1.0.1-0.</li> <li>See full diff in <a href="https://github.com/digitalbazaar/forge/compare/v1.0.0...v1.1.0">compare view</a></li> </ul> </details> <br /> --- <details> <summary>Dependabot commands</summary> <br /> You can trigger Dependabot actions by commenting on this MR - `$dependabot rebase` will rebase this MR - `$dependabot recreate` will recreate this MR rewriting all the manual changes and resolving conflicts </details>
argoyle commented 2022-01-08 14:45:08 +00:00 (Migrated from gitlab.com)

mentioned in commit 344ef1efcc

mentioned in commit 344ef1efcc8bcda4ae771761d9a1bce81019ba75
argoyle (Migrated from gitlab.com) merged commit 344ef1efcc into main 2022-01-08 14:45:08 +00:00
Sign in to join this conversation.