Feature/https #1
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.
Securized (-ish, really just as a basic deterrent) HTTPS streamer server, using self-signed certificate, and header-based rejection using dynamically-generated UUID (per start/stop session).
Although it is technically possible to generate client key/certificate pairs in addition to the server stuff (the code already does that actually ... but it's disabled because useless), this is totally useless because the CA auth is incorrect anyway, and the chain validation is bypassed by our Electron event handlers.
Also see: readium/r2-streamer-js#15