You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Support custom crypto backends via rustls-no-provider #7059
I'd like to integrate and test rustpython in another project utilizing https://github.com/ctz/graviola and rustls instead of aws-lc-rs. However currently rustpython hard codes aws-lc-rs in the Cargo.toml. Is this something that could be supported?
reqwest has a rustls-no-provider option where you are able to use graviola like this:
fnmain(){
rustls_graviola::default_provider().install_default().unwrap();// ... rest of main function}
However I see that there are a few mentions of aws_lc_rs imports directly in the rustpython stdlib 🤔
Hi! There is no specific reason to stick on aws_lc_rs. That was selected as default because it is the recommendation of rustls team.
Could you help us to patch ssl.rs not to use aws_lc_rs directly?
Activity
youknowone commentedon Feb 9, 2026
Hi! There is no specific reason to stick on aws_lc_rs. That was selected as default because it is the recommendation of rustls team.
Could you help us to patch ssl.rs not to use aws_lc_rs directly?
Modularize rustls as work towards providers
Modularize rustls as work towards providers
Modularize rustls as work towards providers
Modularize rustls as work towards providers
Modularize rustls as work towards providers
Modularize rustls as work towards providers
Modularize rustls as work towards providers
Modularize rustls as work towards providers
Support custom `rustls` providers (#7657)
Support custom `rustls` providers (#7657)