ssi-sdk
ssi-sdk copied to clipboard
Bump github.com/lestrrat-go/jwx/v2 from 2.0.11 to 2.0.21 in /sd-jwt
Bumps github.com/lestrrat-go/jwx/v2 from 2.0.11 to 2.0.21.
Release notes
Sourced from github.com/lestrrat-go/jwx/v2's releases.
v2.0.21 07 Mar 2024
[Security]
[jwe] Added
jwe.Settings(jwe.WithMaxDecompressBufferSize(int64))
to specify the maximum size of a decompressed JWE payload. The default value is 10MB. If you are compressing payloads greater than this and want to decompress it during a call tojwe.Decrypt
, you need to explicitly set a value large enough to hold that data.The same option can be passed to
jwe.Decrypt
to control this behavior on a per-message basis.[jwe] Added documentation stating that
jwe.WithMaxBufferSize
option will be renamed in future versions, i.e. v3v2.0.20 20 Feb 2024
[New Features]
- [jwe] Added
jwe.Settings(WithMaxBufferSize(int64))
to set the maximum size of internal buffers. The default value is 256MB. Most users do not need to change this value.- [jws] Allow
jws.WithCompact()
andjws.WithJSON()
to be passed tojws.Parse()
andjws.Verify()
. These options control the expected serialization format for the JWS message.- [jwt] Add
jwt.WithCompactOnly()
to specify that only compact serialization can be used forjwt.Parse()
. Previously, by virtue ofjws.Parse()
allowing either JSON or Compact serialization format,jwt.Parse()
also alloed JSON serialization where as RFC7519 explicitly states that only compact serialization should be used. For backward compatibility the default behavior is not changed, but you can set this global option for jwt:jwt.Settings(jwt.WithCompactOnly(true))
[Miscellaneous]
- Internal key conversions should now allow private keys to be used in place of public keys. This would allow you to pass private keys where public keys are expected.
v2.0.19
v2.0.19 09 Jan 2024 [New Features] * [jws] Added jws.IsVerificationError to check if the error returned by `jws.Verify` was caused by actual verification step or something else, for example, while fetching a key from datasource
[Security Fixes]
[jws] JWS messages formated in full JSON format (i.e. not the compact format, which consists of three base64 strings concatenated with a '.') with missing "protected" headers could cause a panic, thereby introducing a possiblity of a DoS.
This has been fixed so that the
jws.Parse
function succeeds in parsing a JWS message lacking a protected header. Callingjws.Verify
on this same JWS message will result in a failed verification attempt. Note that this behavior will differ slightly when parsing JWS messages in compact form, which result in an error. </tr></table>
... (truncated)
Changelog
Sourced from github.com/lestrrat-go/jwx/v2's changelog.
v2.0.21 07 Mar 2024 [Security]
[jwe] Added
jwe.Settings(jwe.WithMaxDecompressBufferSize(int64))
to specify the maximum size of a decompressed JWE payload. The default value is 10MB. If you are compressing payloads greater than this and want to decompress it during a call tojwe.Decrypt
, you need to explicitly set a value large enough to hold that data.The same option can be passed to
jwe.Decrypt
to control this behavior on a per-message basis.[jwe] Added documentation stating that
jwe.WithMaxBufferSize
option will be renamed in future versions, i.e. v3v2.0.20 20 Feb 2024 [New Features]
- [jwe] Added
jwe.Settings(WithMaxBufferSize(int64))
to set the maximum size of internal buffers. The default value is 256MB. Most users do not need to change this value.- [jws] Allow
jws.WithCompact()
andjws.WithJSON()
to be passed tojws.Parse()
andjws.Verify()
. These options control the expected serialization format for the JWS message.- [jwt] Add
jwt.WithCompactOnly()
to specify that only compact serialization can be used forjwt.Parse()
. Previously, by virtue ofjws.Parse()
allowing either JSON or Compact serialization format,jwt.Parse()
also alloed JSON serialization where as RFC7519 explicitly states that only compact serialization should be used. For backward compatibility the default behavior is not changed, but you can set this global option for jwt:jwt.Settings(jwt.WithCompactOnly(true))
[Miscellaneous]
- Internal key conversions should now allow private keys to be used in place of public keys. This would allow you to pass private keys where public keys are expected.
v2.0.19 09 Jan 2024 [New Features]
- [jws] Added jws.IsVerificationError to check if the error returned by
jws.Verify
was caused by actual verification step or something else, for example, while fetching a key from datasource[Security Fixes]
[jws] JWS messages formated in full JSON format (i.e. not the compact format, which consists of three base64 strings concatenated with a '.') with missing "protected" headers could cause a panic, thereby introducing a possiblity of a DoS.
This has been fixed so that the
jws.Parse
function succeeds in parsing a JWS message lacking a protected header. Callingjws.Verify
on this same JWS message will result in a failed verification attempt. Note that this behavior will differ slightly when parsing JWS messages in compact form, which result in an error.v2.0.18 03 Dec 2023
... (truncated)
Commits
611d914
Merge pull request #1091 from lestrrat-go/develop/v2551073b
fix keyset suboption documentation (#1090)cdfaccf
silence linter17e2da9
Update Changesd43f2ce
Merge pull request from GHSA-hj3v-m684-v259778ed27
Bump golang.org/x/crypto from 0.19.0 to 0.21.0 (#1086)38d258e
Bump github.com/stretchr/testify from 1.8.4 to 1.9.0 (#1084)ffcb990
Update httprc to v1.0.5 (#1088)c3b3a17
Merge branch 'develop/v2' into v2ace7a77
Update Changes- 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 will merge this PR once 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 show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@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) You can disable automated security fix PRs for this repo from the Security Alerts page.