-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Backport 2.16: Query Mbed TLS configuration from ssl_client2 and ssl_server2 #2389
Backport 2.16: Query Mbed TLS configuration from ssl_client2 and ssl_server2 #2389
Conversation
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 have reviewed the code again, ran the new scripts and make test
and ssl-opt.sh
tests. They all succeed.
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.
This looks to me like a faithful backport of the original PR.
@andresag01 This PR now has conflicts in |
e1d3f46
to
4c47e18
Compare
@mpg: Resolved conflicts. Waiting for CI results |
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.
Re-approving after rebase
@k-stachowiak Please re-review! |
This has 2 approvals and a passing CI, fixes real bugs, has ChangeLog entries and is well covered by pre-existing tests, so ready for merge. |
This PR is a backport for #2105
Description
This PR addresses:
The problem was that the detection of the current configuration in ssl-opt.sh used to be based on a fragile combination of calls to grep and sed which did not work in some cases and is not very portable. This PR replaces that mechanism by extending the command line interface for ssl_client2 and ssl_server2 to allow querying the current Mbed TLS configuration. For example, to check if MBEDLTS_AES_C was enabled at compile time, we simply need to run the command:
A return value of 0 means that the feature is enabled and 1 means it was not. If the macro has a non empty expansion, this will be printed to stdout.
Status
READY