feat: add node-address-bound TLS termination#1029
Draft
samcamwilliams wants to merge 2 commits into
Draft
Conversation
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
1 participant
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.
Adds native TLS termination to HyperBEAM’s normal Cowboy/Ranch listener.
Certificates are obtained and renewed through a new
~tls@1.0device. The certificate leaf uses the node’s exact RSApriv-walletas the source key, allowing users to check by eye that at the HTTPS connection they have with a HyperBEAM node matches exactly the node's wallet identity.HTTP-01challenges are routed through the normalon/requesthook of the node. Runtime state is held by onehb_nameprocess, with no separate TLS server or OTP supervision tree. Certificate rotation preserves existing connections.Supports HTTP/1.1 and HTTP/2. HTTP/3 is rejected when TLS termination is enabled for now.