-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to golang-jwt v3.2.1 #166
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -28,7 +28,7 @@ import ( | |
"syscall" | ||
"time" | ||
|
||
"github.com/dgrijalva/jwt-go" | ||
"github.com/golang-jwt/jwt" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We still refer to the old library (https://github.com/dgrijalva) in a comment at line 438) in this file in the context of a previous fix. Because it's about clock skew, so I would expect that issue to be also relevant with the new library but I have not put thought into it. Just writing here so that we do not overlook it. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This should be ok. We already fixed that problem on our end and the issue is referenced just to set the context. |
||
"github.com/google/uuid" | ||
"github.com/labstack/echo-contrib/jaegertracing" | ||
"github.com/labstack/echo-contrib/prometheus" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is
github.com/dgrijalva/jwt-go
still not removed fromgo.sum
? Is it still an indirect dependency? If so, it may still pose a security threat.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, good point, let me check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comes as an indirect dependency from labstack/echo library:
Unfortunately, that library does not have a version including a fix rather they claim not to be effected by the issue: labstack/echo#1916 (comment)
Opened another draft PR with replace however, it is failing with another issue during go mod tidy: #167
Not sure how to proceed here yet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding from that comment is that we are safe in this situation because
labstack/echo
claims no optionalaudience
verification by default. However, we had better keep an eye onv5
oflabstack/echo
where they will get rid of the unmaintainedgithub.jparrowsec.cn/dgrijalva/jwt-go
dependency.Because
labstack/echo
is the only consumer ofgithub.jparrowsec.cn/dgrijalva/jwt-go
and because they claim no optionalaudience
verification by default, I think we are good to go.And we had better get rid of the direct dependency asap.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And if somewhere, we were ourselves doing an optional
audience
verification using the vulnerable library (github.com/dgrijalva/jwt-go
), then it would have been our direct dependency.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@negz, @daren-eth, we may keep an eye on
labstack/echo
andgithub.jparrowsec.cn/dgrijalva/jwt-go
as I had previously observed that we depend on them elsewhere, e.g.,upbound-api
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @turkenh for the investigation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Created this issue to track indirect dependencies: #168