refactor: introduce tls state manager #52
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the fifth commit in the series of incremental refactoring of the current minivpn tree.
In this commit, we introduce the tlsstate package, which is the layer above the control channel
tlsstate is a service worker that will attempt to do a TLS negotiation (wrapped in a control packet), and then use this secure channel to exchange keys with the OpenVPN server and use these keys for encrypting and decrypting payloads in the data channel.
tlsstate waits for a signal in the NotifyTLS channel and then will start the handshake and the key negotiation.
Reference issue: #47