Allow for overriding the OpenSSL security level #203
Merged
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
Owner
|
Great thanks, all working now. Package re released at version 9.1.0. |
Contributor
Author
Awesome, thank you! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
As discussed in #200, this PR adds the ability to override the security level used by OpenSSL. This allows for still using cipher suites like
TLS_PSK_WITH_AES_128_CCM_8that must be supported by CoAP implementations (see section 9.1.3.1 of RFC 7252), as more recent versions of OpenSSL are not allowing them to be used anymore without lowering the security level.The DTLS example is adjusted accordingly so that it now works again.