Open
Conversation
added 3 commits
February 13, 2026 11:22
…lso output if existing encryption keys are found
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
2 participants
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.
Here is the first Baby Steps improvement Pull Request for better encryption key handling .. i've introduced a elasticstack variable which can be used for setting a higher character count to improve security.
Also i've introduced intermediate checking if a already present encryption file exists and provide some output at least that it was found .. // easier debugging
Also adjusting the generation to happening when no file is present .. , so there is no inconsistency when already a file is present and an older key is used for generation of the certificates.
Also admitting that it might not be the greatest improvement - but we need to start somewhere
Regards
David