This repository was archived by the owner on Jan 23, 2023. It is now read-only.
Populate DataHash key size in SslConnectionInfo #3916
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
Member
There was a problem hiding this comment.
We can remove the = 0 from the declaration of DataHashKeySize earlier.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
8 participants
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.
Populating DataHash key size in SslConnectionInfo Structure.
Found out that opnssl doesn't provide a way to return the keyExchange size .. Internally it does some calculations for key size depending upon which keyEx Algo is used.
So that thing is still left .. For now would be tracked under same issue.