Bump github.com/lestrrat-go/jwx/v2 from 2.0.9-0.20230429214153-5090ec1bd2cd to 2.0.10

[dependabot]

Bumps github.com/lestrrat-go/jwx/v2 from 2.0.9-0.20230429214153-5090ec1bd2cd to 2.0.10.

Release notes

Sourced from github.com/lestrrat-go/jwx/v2's releases.

v2.0.10

v2.0.10 - 12 Jun 2023
[New Features]
  * [jwe] (EXPERIMENTAL) Added `jwe.KeyEncrypter` and `jwe.KeyDecrypter` interfaces
    that works in similar ways as how `crypto.Signer` works for signature
    generation and verification. It can act as the interface for your encryption/decryption
    keys that are for example stored in an hardware device.
This feature is labeled experimental because the API for the above interfaces have not
been battle tested, and may need to changed yet. Please be aware that until the API
is deemed stable, you may have to adapat our code to these possible changes,
_even_ during minor version upgrades of this library.

[Bug fixes]


Registering JWS signers/verifiers did not work since v2.0.0, because the
way we handle algorithm names changed in 2aa98ce6884187180a7145b73da78c859dd46c84.
(We previously thought that this would be checked by the example code, but it
apparently failed to flag us properly)
The logic behind managing the internal database has been fixed, and
jws.RegisterSigner and jws.RegisterVerifier now properly hooks into the new
jwa.RegisterSignatureAlgorithm to automatically register new algorithm names
(#910, #911)
[Miscellaneous]


Added limited support for github.com/segmentio/asm/base64. Compile your code
with the jwx_asmbase64 build tag. This feature is EXPERIMENTAL.
Through limited testing, the use of a faster base64 library provide 1~5% increase
in throughput on average. It might make more difference if the input/output is large.
If you care about this performance improvement, you should probably enable
goccy JSON parser as well, by specifying jwx_goccy,jwx_asmbase64 in your build call.


Slightly changed the way global variables underneath jwk.Fetch are initialized and
configured. jwk.Fetch creates an object that spawns wokers to fetch JWKS when it's
first called.
You can now also use jwk.SetGlobalFetcher() to set a fetcher object which you can
control.

v2.0.9

v2.0.9 - 21 Mar 2023
[Security Fixes]
  * Updated use of golang.org/x/crypto to v0.7.0
[Bug fixes]
  * Emitted PEM file for EC private key types used the wrong PEM armor ([#875](https://github.com/lestrrat-go/jwx/issues/875))
[Miscellaneous]
  * Banners for generated files have been modified to allow tools to pick them up ([#867](https://github.com/lestrrat-go/jwx/issues/867))
  * Remove unused variables around ReadFileOption ([#866](https://github.com/lestrrat-go/jwx/issues/866))
  * Fix test failures
</tr></table> 

... (truncated)

Changelog

Sourced from github.com/lestrrat-go/jwx/v2's changelog.

v2.0.10 - 12 Jun 2023 [New Features]

• [jwe] (EXPERIMENTAL) Added jwe.KeyEncrypter and jwe.KeyDecrypter interfaces that works in similar ways as how crypto.Signer works for signature generation and verification. It can act as the interface for your encryption/decryption keys that are for example stored in an hardware device.

  This feature is labeled experimental because the API for the above interfaces have not been battle tested, and may need to changed yet. Please be aware that until the API is deemed stable, you may have to adapat our code to these possible changes, even during minor version upgrades of this library.

[Bug fixes]

• Registering JWS signers/verifiers did not work since v2.0.0, because the way we handle algorithm names changed in 2aa98ce6884187180a7145b73da78c859dd46c84. (We previously thought that this would be checked by the example code, but it apparently failed to flag us properly)

  The logic behind managing the internal database has been fixed, and jws.RegisterSigner and jws.RegisterVerifier now properly hooks into the new jwa.RegisterSignatureAlgorithm to automatically register new algorithm names (#910, #911) [Miscellaneous]

• Added limited support for github.com/segmentio/asm/base64. Compile your code with the jwx_asmbase64 build tag. This feature is EXPERIMENTAL.

  Through limited testing, the use of a faster base64 library provide 1~5% increase in throughput on average. It might make more difference if the input/output is large. If you care about this performance improvement, you should probably enable goccy JSON parser as well, by specifying jwx_goccy,jwx_asmbase64 in your build call.

• Slightly changed the way global variables underneath jwk.Fetch are initialized and configured. jwk.Fetch creates an object that spawns wokers to fetch JWKS when it's first called. You can now also use jwk.SetGlobalFetcher() to set a fetcher object which you can control.

v2.0.9 - 21 Mar 2023 [Security Fixes]

• Updated use of golang.org/x/crypto to v0.7.0 [Bug fixes]

• Emitted PEM file for EC private key types used the wrong PEM armor (#875) [Miscellaneous]

• Banners for generated files have been modified to allow tools to pick them up (#867)

• Remove unused variables around ReadFileOption (#866)

• Fix test failures

• Support bazel out of the box

• Now you can create JWS messages using {"alg":"none"}, by calling jws.Sign() with jws.WithInsecureNoSignature() option. (#888, #890).

  Note that there is no way to call

... (truncated)

Commits

• See full diff 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 will merge this PR once it's up-to-date and CI passes on it, as requested by @decentralgabe.

---

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 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)

[decentralgabe]

@dependabot squash and merge