Use TLS from Memory #1419
Closed
Use TLS from Memory #1419
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
|
Please remove this pr I see that the function is provided in TLSConfig. Thank You. |
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 PR adds using TLS from memory in addition to a file location. It provides a easier deployment for edge/iot devices from a single binary without the need to expose certificates on the file system.
The use case is to help deploying to a large number of clients using a single binary for initial setup.
Testing added to conn_test.go at TestClientCertificateMem to test server and client certificates. This tests both features being proposed.
Tested on Linux and Android.