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

proto: allow rustls::ClientConfig without initial suite #1859

Merged
merged 2 commits into from May 14, 2024

Conversation

djc
Copy link
Collaborator

@djc djc commented May 12, 2024

No description provided.

@djc djc requested a review from Ralith May 12, 2024 19:20
@djc
Copy link
Collaborator Author

djc commented May 12, 2024

Hmm, maybe we should also implement TryFrom for Arc<rustls::ClientConfig>?

@djc djc force-pushed the separate-initial-suite branch 2 times, most recently from 72a54d1 to 2c7a656 Compare May 12, 2024 19:37
@Ralith
Copy link
Collaborator

Ralith commented May 13, 2024

Hmm, maybe we should also implement TryFrom for Arcrustls::ClientConfig?

Oops, yes, I think we should have done this from the start. Luckily I don't think there's a drawback to having both... maybe slightly worse inference in rare cases.

@M0dEx
Copy link

M0dEx commented May 13, 2024

Tested locally in quincy and it seems to be working.

@djc
Copy link
Collaborator Author

djc commented May 14, 2024

Oops, yes, I think we should have done this from the start. Luckily I don't think there's a drawback to having both... maybe slightly worse inference in rare cases.

Added this in a second commit.

Also changed the first commit to actually check that the specified Suite is actually AES-128-GCM-SHA256.

@djc djc merged commit 8bd0600 into main May 14, 2024
8 checks passed
@djc djc deleted the separate-initial-suite branch May 14, 2024 16:53
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.

None yet

3 participants