Add support for automatic TLS encryption via autocert #402
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
cristinaleonr
approved these changes
May 7, 2024
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 support for enabling TLS automatically via the autocert package. In particular, the two new flags
-autocert.enabledand-autocert.hostnameenable this feature. On the first HTTPS request, ndt-server will automatically try to get a certificate from LetsEncrypt, assuming the requested hostname matches what's in the-autocert.hostnamefile.The reason for it being a file is that the in the BYOS scenario the hostname is generated by the autojoin
registerclient and written to a file.(FYI @nkinkade )
This change is