Repository navigation
CMO: TLS in transit + mTLS (#27) - #36
Merged
Merged
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
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.
Plan item #27: TLS in transit, with optional mTLS.
BUILD_TLS=yes(libssl-dev in build, libssl3 + openssl at runtime)CMO_TLS_CERT/KEY/CAturns ontls-port(default 6380), TLS 1.2/1.3 only, TLS for replication and cluster bus.CMO_TLS_MTLS=yesrequires client certs;CMO_TLS_ONLY=yescloses the plain port. Missing or unreadable files stop startup.deploy/tls-gen.sh: private CA + server/client certs, keys 0600Checked:
sh -non the entrypoint; tls-gen output verifies against its CA with the right SANs. Not checked: an image build and a live TLS connection, because the box has no make/cmake. CI image build or a home-labdocker buildshould confirm. Not deployed.