Skip to content
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

Add tls.Config.CurveGuess to allow specifying which keyshares to send #155

Merged
merged 1 commit into from
Oct 2, 2023

Conversation

bwesterb
Copy link
Member

@bwesterb bwesterb commented Sep 28, 2023

No description provided.

@bwesterb bwesterb requested a review from Lekensteyn September 28, 2023 13:46
@bwesterb bwesterb force-pushed the bas/custom-keyshares branch from cc5fc76 to 87c022f Compare September 28, 2023 15:12
@SulemanAhmadd SulemanAhmadd requested review from SulemanAhmadd and removed request for SulemanAhmadd September 28, 2023 17:41
@bwesterb bwesterb force-pushed the bas/custom-keyshares branch 2 times, most recently from 48f3f66 to 5a7dd4f Compare September 29, 2023 15:31
src/crypto/tls/common.go Outdated Show resolved Hide resolved
src/crypto/tls/handshake_client.go Outdated Show resolved Hide resolved
@bwesterb bwesterb force-pushed the bas/custom-keyshares branch from 5b42f1d to 8cc8f19 Compare September 29, 2023 16:59
Copy link
Contributor

@Lekensteyn Lekensteyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Interesting detail that is not documented here: some implementations (OpenSSL) use the order of ClientCurveGuess (key_shares) to select the final key share. Others (boringssl, Go crypto/tls) determine the expected key share based on the CurvePreferences (supported_groups) setting.

@bwesterb bwesterb merged commit ef1765f into cf Oct 2, 2023
2 checks passed
@bwesterb bwesterb deleted the bas/custom-keyshares branch October 2, 2023 11:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants