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.

Sign up for GitHub

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

Jump to bottom

proposal: crypto/tls: add ConnectionState.CurveID #67516

Open
FiloSottile opened this issue May 19, 2024 · 1 comment
Open

proposal: crypto/tls: add ConnectionState.CurveID #67516

FiloSottile opened this issue May 19, 2024 · 1 comment
Labels
Proposal Proposal-Crypto Proposal related to crypto packages or other security issues
Milestone
Proposal

Comments

@FiloSottile
Copy link
Contributor

Proposal Details

With #67061, the selected "CurveID" is the difference between a post-quantum connection and not. We should expose it in ConnectionState. I actually assumed we were already exposing this.

It's unfortunate to use the CurveID misnomer, but ConnectionState doesn't feel like the place to start introducing a new name, it will only cause confusion.

/cc @golang/security
@FiloSottile FiloSottile added Proposal Proposal-Crypto Proposal related to crypto packages or other security issues labels May 19, 2024
@gopherbot gopherbot added this to the Proposal milestone May 19, 2024
@FiloSottile
Copy link
Contributor Author

If a deprecated RSA KEX is used, CurveID will be zero.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Proposal Proposal-Crypto Proposal related to crypto packages or other security issues
Projects
Proposals
Status: Incoming
Milestone
Proposal
Development

No branches or pull requests
2 participants
@FiloSottile @gopherbot