Mirage TLS support#37
Merged
Merged
Conversation
This was referenced Jan 14, 2015
7ff782d to
b666083
Compare
This was referenced Jan 15, 2015
This simplifies the code and will make it easier to wrap TLS flows.
Member
|
This does not compile with |
Contributor
Author
|
0.3.0 is too old. It should work with the tls Git master. |
Member
|
Ok, so this needs a new release of |
Member
|
@samoht yes, this is true... and will happen soon. to work on xen, I believe gmp and zarith from mirage-dev need to be upstreamed as well |
9a7c86b to
f20312a
Compare
Member
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
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.
The first patch makes use of the new
error_messagefunction in mirage/mirage#346 to simplify error handling for flows.The second patch adds TLS support. It's used like this:
i.e. you pass in a TLS configuration and an underlying conduit specification and it wraps it.