-
Notifications
You must be signed in to change notification settings - Fork 348
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
doc: add a disclamer for the TLS handshake timeouts TL;DR bug in godebug.md #311
Conversation
This PR (HEAD: 7f2a9ac) has been imported to Gerrit for code review. Please visit Gerrit at https://go-review.googlesource.com/c/website/+/650857. Important tips:
|
Message from Ian Lance Taylor: Patch Set 1: Commit-Queue+1 Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
Message from Go LUCI: Patch Set 1: Dry run: CV is trying the patch. Bot data: {"action":"start","triggered_at":"2025-02-20T21:01:29Z","revision":"696074edffe0959d32fdc97117bfdf9ca7318ea9"} Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
Message from Ian Lance Taylor: Patch Set 1: -Commit-Queue Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
Message from Go LUCI: Patch Set 1: This CL has passed the run Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
Message from Go LUCI: Patch Set 1: LUCI-TryBot-Result+1 Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
Message from Roland Shoemaker: Patch Set 1: (4 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
This PR (HEAD: a709e6f) has been imported to Gerrit for code review. Please visit Gerrit at https://go-review.googlesource.com/c/website/+/650857. Important tips:
|
Message from Thomas Vaillant: Patch Set 2: (4 comments) Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
Message from Roland Shoemaker: Patch Set 2: Code-Review+2 Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
…bug.md Relates to golang/go#71257. Since post-quantum TLS algorithms are enabled by default, we should warn about the possible bugs with legacy servers (see https://tldr.fail/) Change-Id: Id5a565c2959c5b0f7b8bdd53ce9e70b191c4bf38 GitHub-Last-Rev: a709e6f GitHub-Pull-Request: #311 Reviewed-on: https://go-review.googlesource.com/c/website/+/650857 Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Roland Shoemaker <[email protected]> Auto-Submit: Ian Lance Taylor <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
Message from Ian Lance Taylor: Patch Set 2: Auto-Submit+1 Code-Review+1 Commit-Queue+1 Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
Message from Go LUCI: Patch Set 2: Dry run: CV is trying the patch. Bot data: {"action":"start","triggered_at":"2025-02-20T23:03:48Z","revision":"a2906b7f41fbfeeeccc43c8f40b518e6535adb20"} Please don’t reply on this GitHub thread. Visit golang.org/cl/650857. |
This PR is being closed because golang.org/cl/650857 has been merged. |
Relates to golang/go#71257. Since post-quantum TLS algorithms are enabled by default, we should warn about the possible bugs with legacy servers (see https://tldr.fail/)