I have found these related issues/pull requests
Relates to #1
Description
When building Rust applications in FIPS mode, it's important to be cognizant of which cryptographic algorithms are being included in the application, and to ensure they are FIPS-validated.
The sqlx-mysql crate automatically pulls in sha1 for mysql_native_password, and I need a way to exclude it from the final binary.
Prefered solution
It'd be great if the crate supported explicitly disabling mysql_native_password so that the sha1 implementation never makes it into the final binary.
Is this a breaking change? Why or why not?
It's possible to structure the default features to make this non-breaking, I think?
I have found these related issues/pull requests
Relates to #1
Description
When building Rust applications in FIPS mode, it's important to be cognizant of which cryptographic algorithms are being included in the application, and to ensure they are FIPS-validated.
The
sqlx-mysqlcrate automatically pulls insha1formysql_native_password, and I need a way to exclude it from the final binary.Prefered solution
It'd be great if the crate supported explicitly disabling
mysql_native_passwordso that thesha1implementation never makes it into the final binary.Is this a breaking change? Why or why not?
It's possible to structure the default features to make this non-breaking, I think?