-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to wolfssl 5.7.2 #178
Conversation
We already emitted a `rerun-if-changed` for the directory itself which is highly likely to get a different `mtime` if a file within it changed, and we have not observed issues with the previous arrangements in practice, but this change should make things more explicit.
Moving from v5.6.6-stable we are picking up: https://github.com/wolfSSL/wolfssl/releases/tag/v5.7.0-stable https://github.com/wolfSSL/wolfssl/releases/tag/v5.7.2-stable (there was no 5.7.1) Our `disable-falcon-dilithium.patch` required an update, likely due to the changes in wolfSSL/wolfssl#7622.
Code coverage summary for dd54cea:
✅ Region coverage 58% passes |
@@ -118,6 +118,8 @@ fn build_wolfssl(wolfssl_src: &Path) -> PathBuf { | |||
.enable("supportedcurves", None) | |||
// Enable TLS/1.3 | |||
.enable("tls13", None) | |||
// Enable liboqs, etc | |||
.enable("experimental", None) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this flag needed even if we use liboqs instead of wolfssl builtin kyber ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so, configure script contains:
# KYBER
# Used:
# - SHA3, Shake128 and Shake256
AC_ARG_ENABLE([kyber],
[AS_HELP_STRING([--enable-kyber],[Enable KYBER (requires --enable-experimental) (default: disabled)])],
[ ENABLED_KYBER=$enableval ],
[ ENABLED_KYBER=no ]
)
Moving from v5.6.6-stable we are picking up:
(there was no 5.7.1)
Our
disable-falcon-dilithium.patch
required an update, likely due to the changes in wolfSSL/wolfssl#7622.