Skip to content

Switch rustls crypto provider from ring to aws-lc-rs - #3654

Draft
ChihweiLHBird wants to merge 1 commit into
spinframework:mainfrom
ChihweiLHBird:zhiwei/ring-to-aws-lc-rs
Draft

Switch rustls crypto provider from ring to aws-lc-rs#3654
ChihweiLHBird wants to merge 1 commit into
spinframework:mainfrom
ChihweiLHBird:zhiwei/ring-to-aws-lc-rs

Conversation

@ChihweiLHBird

Copy link
Copy Markdown
Contributor

Install aws-lc-rs as the process-wide provider at startup. ring is still compiled via transitive rustls features; removing it is a follow-up.

Since both provider features are now enabled, rustls auto-detection would panic on paths that bypass Spin's entrypoints. Replace the install helper with spin_tls::get_or_install_default_crypto_provider(), which returns the installed default - respecting a provider installed by embedders (the old helper would panic) - and installs aws-lc-rs if none is set. The outbound client and trigger-http server TLS configs now build with this provider explicitly.

Partially fix #3502

Install aws-lc-rs as the process-wide provider at startup. ring is still compiled via transitive rustls features; removing it is a follow-up.

Since both provider features are now enabled, rustls auto-detection would panic on paths that bypass Spin's entrypoints. Replace the install helper with spin_tls::get_or_install_default_crypto_provider(), which returns the installed default - respecting a provider installed by embedders (the old helper would panic) - and installs aws-lc-rs if none is set. The outbound client and trigger-http server TLS configs now build with this provider explicitly.

Signed-off-by: Zhiwei Liang <zhiwei.liang@zliang.me>
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.

FIPS Support

1 participant