update jwt-go version to remove vulnerability #1713
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@lammel Thanks for pointing that out. Is there a hesitation to fixing this? Or is a longer-term fix being considered? |
|
See discussion in #1663. Basically jwt-go seems unmaintained, using a Using the go-jwt v4 branch (preview1) is one of the options. It seems other projects also hesitate with the decission. |
|
@lammel That makes sense. I agree, it's probably the right call to move to using a library that is more maintained. I'll just close this PR and keep an eye out for when this issue is addressed. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #1712