chore(deps): update module gopkg.in/go-jose/go-jose.v2 to v4 #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.6.3
->v4.0.4
Release Notes
go-jose/go-jose (gopkg.in/go-jose/go-jose.v2)
v4.0.4
Compare Source
Fixed
breaking change. See #136 / #137.
v4.0.3
Compare Source
Changed
v4.0.2
Compare Source
Changed
argument type (#104)
curves error cases (#117)
v4.0.1
Compare Source
Fixed
amounts of memory and CPU when decompressed by
Decrypt
orDecryptMulti
.Those functions now return an error if the decompressed data would exceed
250kB or 10x the compressed size (whichever is larger). Thanks to
Enze Wang@Alioth and Jianjun Chen@Zhongguancun Lab (@zer0yu and @chenjj)
for reporting.
v4.0.0
Compare Source
This release makes some breaking changes in order to more thoroughly
address the vulnerabilities discussed in Three New Attacks Against JSON Web
Tokens, "Sign/encrypt confusion", "Billion hash attack", and "Polyglot
token".
Changed
ParseSigned, ParseDetached, jwt.ParseEncrypted, jwt.ParseSigned,
jwt.ParseSignedAndEncrypted (#69, #74)
to use and it's a mistake to allow unexpected algorithms. For instance the
"billion hash attack" relies in part on programs accepting the PBES2
encryption algorithm and doing the necessary work even if they weren't
specifically configured to allow PBES2.
Added
ParseEncrypted, which try to automatically detect which serialization was
provided. It's common to require a specific serialization for a specific
protocol - for instance JWT requires Compact serialization.
v3.0.3
: Version 3.0.3Compare Source
Fixed
v3.0.2
Compare Source
Fixed
Changed
Added
v3.0.1
Compare Source
Fixed
JSONWebEncryption.Decrypt and JSONWebEncryption.DecryptMulti to consume large
amounts of CPU, causing a DoS. Thanks to Matt Schwager (@mschwager) for the
disclosure and to Tom Tervoort for originally publishing the category of attack.
https://i.blackhat.com/BH-US-23/Presentations/US-23-Tervoort-Three-New-Attacks-Against-JSON-Web-Tokens.pdf
v3.0.0
: Version 3.0.0Compare Source
First release after moving from square/go-jose to the new go-jose/go-jose repository.
Fixes & Improvements
a10ff54
- Fix for EC thumbprint template so we compute EC thumbprints correctly30f4a6a
- Treat zero Expected.Time as now in Claims.Validate when verifying JWTs4ac8eda
- Fix handling of the x5u header (X.509 certificate URL) in JWKsd7b900b
- Strip padding off base64 strings, to match spec per RFC7515 Appendix C7f81482
- Extract key from JWKs to ensure you can use it when verifying a detached signaturee225b2d
- Support non-pointer JWKs to match behavior for other key types94cbec2
- Useed25519
from the stdlib instead of the golang.org/x/crypto versioneae0da4
- Export jose-util helpers as they might be useful for others4bac79d
- Fix issue square#182 that caused panic on claims with invalid JWT payload60a6e9d
- Use string.Builder to remove whitespace, instead of a regexp to improve performance2009556
- Better error handling to avoid panic that can be caused by invalid headersThis release also cleans up a number of module references for the new repo migration, fixed some typos in comments, and more.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "at 10am on Monday except on 25th of December in 2023 and 1st of January 2024 and 1st of April 2024 and 20th of May 2024 and 19th of August 2024" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.