Skip to content

fix: use aws_lc_rs rustls CryptoProvider in workspace#436

Open
ianderson-nvidia wants to merge 1 commit intoNVIDIA:mainfrom
ianderson-nvidia:standardize_aws_lc_rs
Open

fix: use aws_lc_rs rustls CryptoProvider in workspace#436
ianderson-nvidia wants to merge 1 commit intoNVIDIA:mainfrom
ianderson-nvidia:standardize_aws_lc_rs

Conversation

@ianderson-nvidia
Copy link
Contributor

@ianderson-nvidia ianderson-nvidia commented Mar 4, 2026

Description

The default feature of the rustls crate uses the aws_lc_rs crate, aws_lc_rs is a ring-compatible crypto library
https://docs.rs/rustls/latest/rustls/crypto/struct.CryptoProvider.html

Some crates were calling crypto::ring::install_default() directly which were updated to use aws_lc_rs

Type of Change

  • Add - New feature or capability
  • Change - Changes in existing functionality
  • Fix - Bug fixes
  • Remove - Removed features or deprecated functionality
  • [ X] Internal - Internal changes (refactoring, tests, docs, etc.)

Related Issues (Optional)

Breaking Changes

  • This PR contains breaking changes

Testing

  • Unit tests added/updated
  • Integration tests added/updated
  • Manual testing performed
  • No testing required (docs, internal refactor, etc.)

Additional Notes

aws_lc_rs also supports FIPS140-3 Cryptogrpahy

@ianderson-nvidia ianderson-nvidia requested a review from a team as a code owner March 4, 2026 02:12
@copy-pr-bot
Copy link

copy-pr-bot bot commented Mar 4, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Signed-off-by: Ian Anderson <ianderson@nvidia.com>
@wminckler
Copy link
Contributor

my understanding is that the code is actually still using the same provider? its just the method in which we get that has changed?

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