fix: probe for all AES_GCM ktls variants #4295
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
On some linux platforms, only the
AES_GCM_128
ktls definitions are available. Ideally, we would probe for each cipher independently from one another. However, as a short-term fix, this change adds theAES_GCM_256
variant to the ktls feature probe to avoid build failures.Testing:
I tested this locally with a musl build (which doesn't export
AES_GCM_256
). Our ktls CI tests should prevent regressions.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.