Adds Extended Master Secret to TLS (RFC 7627) #1574
Closed
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.
extms snads for Extended Master Secret, see RFC 7627.
I just needed to do this for myself, so created PR by the way. If it does not comply to the rules or is screwed in any way, I'm probably not spending more time on this...
Did not created unit test, however tested it on few real handshakes. It works. My assumptions:
Based on this, I did the following adjustments:
tls_session_updateonTLSServerHellorecord looks for the extension and notes its usage into the session objecttls_session_updateonClientKeyExchangegathers all handshake messages into one binary string and computes the hash on it. By that time, all should be available.compute_master_secretmethod.