dependabot[bot] opened a new pull request, #2185: URL: https://github.com/apache/dubbo-go/pull/2185
Bumps [github.com/hashicorp/vault/sdk](https://github.com/hashicorp/vault) from 0.6.2 to 0.7.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/hashicorp/vault/blob/main/CHANGELOG.md";>github.com/hashicorp/vault/sdk's changelog</a>.</em></p> <blockquote> <h2>0.7.0 (March 21th, 2017)</h2> <p>SECURITY:</p> <ul> <li>Common name not being validated when <code>exclude_cn_from_sans</code> option used in <code>pki</code> backend: When using a role in the <code>pki</code> backend that specified the <code>exclude_cn_from_sans</code> option, the common name would not then be properly validated against the role's constraints. This has been fixed. We recommend any users of this feature to upgrade to 0.7 as soon as feasible.</li> </ul> <p>DEPRECATIONS/CHANGES:</p> <ul> <li>List Operations Always Use Trailing Slash: Any list operation, whether via the <code>GET</code> or <code>LIST</code> HTTP verb, will now internally canonicalize the path to have a trailing slash. This makes policy writing more predictable, as it means clients will no longer work or fail based on which client they're using or which HTTP verb they're using. However, it also means that policies allowing <code>list</code> capability must be carefully checked to ensure that they contain a trailing slash; some policies may need to be split into multiple stanzas to accommodate.</li> <li>PKI Defaults to Unleased Certificates: When issuing certificates from the PKI backend, by default, no leases will be issued. If you want to manually revoke a certificate, its serial number can be used with the <code>pki/revoke</code> endpoint. Issuing leases is still possible by enabling the <code>generate_lease</code> toggle in PKI role entries (this will default to <code>true</code> for upgrades, to keep existing behavior), which will allow using lease IDs to revoke certificates. For installations issuing large numbers of certificates (tens to hundreds of thousands, or millions), this will significantly improve Vault startup time since leases associated with these certificates will not have to be loaded; however note that it also means that revocation of a token used to issue certificates will no longer add these certificates to a CRL. If this behavior is desired or needed, consider keeping leases enabled and ensuring lifetimes are reasonable, and issue long-lived certificates via a different role with leases disabled.</li> </ul> <p>FEATURES:</p> <ul> <li><strong>Replication (Enterprise)</strong>: Vault Enterprise now has support for creating a multi-datacenter replication set between clusters. The current replication offering is based on an asynchronous primary/secondary (1:N) model that replicates static data while keeping dynamic data (leases, tokens) cluster-local, focusing on horizontal scaling for high-throughput and high-fanout deployments.</li> <li><strong>Response Wrapping & Replication in the Vault Enterprise UI</strong>: Vault Enterprise UI now supports looking up and rotating response wrapping tokens, as well as creating tokens with arbitrary values inside. It also now supports replication functionality, enabling the configuration of a replication set in the UI.</li> <li><strong>Expanded Access Control Policies</strong>: Access control policies can now specify allowed and denied parameters -- and, optionally, their values -- to</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/hashicorp/vault/commit/614deacfca3f3b7162bbf30a36d6fc7362cd47f0";><code>614deac</code></a> Cut version 0.7.0</li> <li><a href="https://github.com/hashicorp/vault/commit/89160f82f15f11630bc79e680fd1fecc2c4cdbb9";><code>89160f8</code></a> Bump for 0.7 release</li> <li><a href="https://github.com/hashicorp/vault/commit/3f67ab489af9c82ec0cabe141163260cf3e2fded";><code>3f67ab4</code></a> Ensure CN check is made when exclude_cn_from_sans is used</li> <li><a href="https://github.com/hashicorp/vault/commit/a5d1808efe3a2f58acfaed2b87c3fbef22c470bf";><code>a5d1808</code></a> Always include a hash of the public key and "vault" (to know where it (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/2498";>#2498</a>)</li> <li><a href="https://github.com/hashicorp/vault/commit/6f84f7ffd04c567eba7ab15516cc42a6613eb2f8";><code>6f84f7f</code></a> Adding allow_user_key_ids field to SSH role config (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/2494";>#2494</a>)</li> <li><a href="https://github.com/hashicorp/vault/commit/02921e87291c27153ab5f4ad0b938ca834de2825";><code>02921e8</code></a> Fix layout for replication</li> <li><a href="https://github.com/hashicorp/vault/commit/db814cee9ef0cada1deecd6ad9c4ea8296c403ed";><code>db814ce</code></a> changelog++</li> <li><a href="https://github.com/hashicorp/vault/commit/5252de6c2b6a7fec3b2faa7fcd2da510ad74e62c";><code>5252de6</code></a> Bump test timeout</li> <li><a href="https://github.com/hashicorp/vault/commit/688104e69a34f883e0c047474902aaf97ded6549";><code>688104e</code></a> Allow roles to specify whether CSR SANs should be used instead of (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/2489";>#2489</a>)</li> <li><a href="https://github.com/hashicorp/vault/commit/38d70b7eb70e07bc5973946d1f9fc4581759c718";><code>38d70b7</code></a> Vault_Enterprise_WWW (<a href="https://github-redirect.dependabot.com/hashicorp/vault/issues/2327";>#2327</a>)</li> <li>Additional commits viewable in <a href="https://github.com/hashicorp/vault/compare/v0.6.2...v0.7.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org For additional commands, e-mail: notifications-h...@dubbo.apache.org
