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
In one of our projects we use mbedtls with time support explicitly switched off. (Context: we are deliberately verifying x509 certificates which have expired validity)
We use this project to produce python packages for various platforms, including windows. We were surprised to find that time validity checks kept failing on windows even though the feature was switched off, and it took some time to track it down to these mysterious lines:
mbedtls-platform-support = { version = "0.1", path = "../mbedtls-platform-support", features = [
"time",
] }
We worked around this with an internal fork, but we wonder why these lines are there in the first place? mbedtls seems to build fine with MBEDTLS_HAVE_TIME + MBEDTLS_HAVE_TIME_DATE undefined?
The text was updated successfully, but these errors were encountered:
In one of our projects we use mbedtls with
time
support explicitly switched off. (Context: we are deliberately verifying x509 certificates which have expired validity)We use this project to produce python packages for various platforms, including windows. We were surprised to find that time validity checks kept failing on windows even though the feature was switched off, and it took some time to track it down to these mysterious lines:
rust-mbedtls/mbedtls/Cargo.toml
Lines 69 to 73 in 68fdeb6
We worked around this with an internal fork, but we wonder why these lines are there in the first place? mbedtls seems to build fine with
MBEDTLS_HAVE_TIME
+MBEDTLS_HAVE_TIME_DATE
undefined?The text was updated successfully, but these errors were encountered: