Enable https to use a dynamically generated self-signed identity #1
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
|
Made a couple slight modifications: 7a2620c - rationale: Didn't want to force application developers into using the a8d2bf1 - rationale: I can envision a boot phase that loads keys and certs from a shared keystore, allowing properly CA-signed certs (rather than self-signed). This would also be "dynamic", so the term "auto" seems to fit the bill here more, IMO. |
jaredhanson
added a commit
that referenced
this pull request
Sep 22, 2014
Enable https to use a dynamically generated self-signed identity
|
Auto is a better name, thanks :) |
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.
Useful for encryption-only SSL modes.