crypto/tls: support RA-TLS challenge extension in ClientHello #77714
❌ Missing CLA from one or more contributors
We couldn't find a Contributor License Agreement (CLA) for some of the contributors shown below. All contributors listed must be covered under a CLA for this pull request to be merged.
📝 If you are not currently covered under a CLA, please visit https://cla.developers.google.com/. Once you've signed, follow the "New Contributors" link at the bottom of this page to update this check.
Help! I've signed the CLA, but it's still showing me as unsigned.
Individual signers
- It's possible we don't have your GitHub username. Verify that your existing CLA data is accurate.
- You may not be using the email associated with your CLA in your Git commits. Check that the email set on your git commits matches the email associated with your CLA.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the same email used in your Git commits. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
- You may have Keep my email address private enabled. Without a visible email address, the CLA cannot be checked. Uncheck it and re-create the offending commit, or have your CLA point of contact add your @users.noreply.github.com address to the CLA group.
ℹ️ Googlers: Go here to view more details and manage scans for this pull request.
🔁 New Contributors: Update this check after signing the CLA by clicking here.
Details
The following contributors were found for this pull request:
❌ 1de8bde Author: @bfoing <40759640+bfoing@users.noreply.github.com>
✅ 28ac8d2 Committer: @cagedmantis <ca***s@golang.org>
✅ 4e531b2 Committer: @cherrymui <ch****yz@google.com>
✅ eaf3bc7 Author: @gopherbot <g***t@golang.org>
✅ 5ba37a3 Committer: @dr2chase <dr****e@google.com>
✅ d5987bf Author: @rolandshoemaker <br*****ll@google.com>, <ro***d@golang.org>
✅ ea603ee Committer: @mknyszek <mk****ek@google.com>
✅ c72fcab Author: @matloob <ma****b@golang.org>
✅ 93f5d1c Author: @qmuntal <qui*****al@gmail.com>
✅ ebee011 Author: @dolmen <oliv*******gue@gmail.com>
✅ 9d497df Author: @neild <d***l@google.com>
✅ a86792b Author: @millerresearch <mill*******rch@gmail.com>
✅ 7d57009 Author: @database64128 <fre*****48@hotmail.com>
✅ c7d189e Author: @FiloSottile <fi****o@golang.org>
✅ be61132 Author: @aarzilli <aless*********illi@gmail.com>
✅ f3dc4aa Author: @9muir <sj***r@google.com>
✅ 90f72bd Committer: @prattmic <mp***t@google.com>
✅ 738bc3a Author: @randall77 <k**@golang.org>
✅ 0b53e41 Author: @ianlancetaylor <i**t@golang.org>
✅ 79ec0c9 Author: <g**@google.com>
✅ b191009 Author: @thatnealpatel <ne*****el@google.com>
✅ 9fd3ac8 Author: @ethanalee-work <et*****ee@google.com>
✅ f7bce4b Author: @nicholashusin <h***n@google.com>, <n**@golang.org>
✅ 14f50f6 Author: @cuonglm <cuon********.vn@gmail.com>
✅ e1ce1bf Author: @jub0bs <jub0********loud@gmail.com>
✅ ea603ee Author: @vasi <d**e@vasilevsky.ca>
✅ 6f07a57 Author: @jkrishmys <jayan***********urthy@ibm.com>
(Only the first commit for a unique contributor is listed.)