-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
regenerate certs #13021
regenerate certs #13021
Conversation
While fixing the TLS issue I found a race:
|
I am addressing the race in another PR, this PR fix the flaky test. |
Jenkins test this please |
Pass the `net.Conn` object when creating the client instead of passing it to the `Handle()` method that keep a reference to it. By doing this we do not have to worry about read or write race over the internal field. The client still need a reference to the connection when the out of bound call to `Close()` is executed to make sure we are getting out of a `Read()` call early. Tested with : ``` while true; do go test -v -race; done ``` Found in elastic#13021
rebasing.. issues with seccomp capabilities? |
jenkins test this please, restarted because of github issue :( |
as @mikemadden42 pointed out this affect 7.3 branch too and would need to be backported. |
@kaiyan-sheng since you have opened the original issues and skipped the test can you review this? |
(cherry picked from commit cffc5a5)
(cherry picked from commit cffc5a5)
(cherry picked from commit cffc5a5)
(cherry picked from commit bc3bb8e)
(cherry picked from commit bc3bb8e)
Fix issue about about weak certs.
It appear the certificate were generated with an older version of openssl and openssl 1.1 have changed the default and is more strict now. I presume it was updated on the CI box.
Fixes: #13009