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

feat: rustls_platform_verifier::tls_config_with_provider #86

Merged
merged 1 commit into from
Apr 9, 2024

Conversation

jbr
Copy link
Contributor

@jbr jbr commented Apr 9, 2024

The primary entry point for this crate tls_config is quite convenient, but opting out of that in order to configure a crypto provider adds a bit more complexity and opportunity for misconfiguration. This PR offers a solution to "do what tls_config does, but with a crypto provider".

based on #81

@jbr jbr force-pushed the tls-config-with-provider branch from 3304d87 to 6aaa0fc Compare April 9, 2024 18:02
@jbr jbr force-pushed the tls-config-with-provider branch 3 times, most recently from dac8d15 to 0260659 Compare April 9, 2024 18:23
Copy link
Member

@cpu cpu left a comment

Choose a reason for hiding this comment

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

Good idea, thank you.

Would you mind updating the README installation and setup section to briefly mention this alongside the existing tls_config() coverage?

@jbr jbr force-pushed the tls-config-with-provider branch 3 times, most recently from 88dd952 to 3751b71 Compare April 9, 2024 18:53
@jbr jbr force-pushed the tls-config-with-provider branch from 3751b71 to 652d61a Compare April 9, 2024 18:56
@jbr jbr force-pushed the tls-config-with-provider branch from 652d61a to e11ad0b Compare April 9, 2024 18:57
@jbr jbr changed the title proposal: rustls_platform_verifier::tls_config_with_provider feat: rustls_platform_verifier::tls_config_with_provider Apr 9, 2024
@complexspaces complexspaces merged commit e2c0224 into rustls:main Apr 9, 2024
16 checks passed
@cpu
Copy link
Member

cpu commented Apr 10, 2024

This was included in v/0.3.1.

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.

3 participants