-
Notifications
You must be signed in to change notification settings - Fork 18k
crypto/tls: panic in TransportTLS handshake in Windows crashes app with panic [1.10 backport] #25033
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
Comments
Moving to 1.10.3 since this won't make it in 1.10.2 @aclements |
@andybons according to @aclements (see above) you won't be able to cherry-pick CL 106275 here. Let me know if and when you want me to build custom solution for this issue. Thank you. Alex |
@alexbrainman Since 1.10.2 is on the way out the door, we can aim for this to be in by 1.10.3 (May 1). Feel free to develop a patch on the release branch at your leisure. No rush since we have a month :) |
Note this should also be included in 1.9.7 (#25034) |
SGTM Alex |
Change https://golang.org/cl/111715 mentions this issue: |
Closed by merging f858dbd to release-branch.go1.10. |
…tChainPolicyPara As discussed in issue #21376, it is unsafe to have syscall.CertChainPolicyPara.ExtraPolicyPara uintptr - it has to be a pointer type. So copy syscall.CertChainPolicyPara into crypto/tls package, make ExtraPolicyPara unsafe.Pointer, and use new struct instead of syscall.CertChainPolicyPara. Fixes #25033 Change-Id: If914af056cbbb0c4d93ffaa915b3d2cb5ecad0cd Reviewed-on: https://go-review.googlesource.com/111715 Reviewed-by: Austin Clements <[email protected]> Run-TryBot: Austin Clements <[email protected]>
@FiloSottile requested issue #21376 to be considered for backport to the next 1.10 minor release.
The text was updated successfully, but these errors were encountered: