-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix: upgrade go-grpc package to fix panic bug #70
Conversation
Signed-off-by: Ashish Tiwari <[email protected]>
Signed-off-by: revolyssup <[email protected]>
Signed-off-by: revolyssup <[email protected]>
Signed-off-by: revolyssup <[email protected]>
Signed-off-by: revolyssup <[email protected]>
@@ -44,4 +44,5 @@ jobs: | |||
- name: Script | |||
run: | | |||
export PATH=$OPENRESTY_PREFIX/nginx/sbin:$PATH | |||
export GODEBUG=x509sha1=1 |
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 do this?
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.
After updating the package, the certs in the tests cannot be used as the tests fail with an error that its insecure to use sha1 algorithm[1]. This runtime flag skips the check[2]
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.
Either this, or we would need to regenerate certificates for tests using something like SHA256. Given these are just tests, I think using this flag is fine.
fixes: #69