Use AES-256 for memberlist message encryption #2140
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
AzraelSec
requested review from
fedepaol,
russellb,
gclawes and
oribon
as code owners
AzraelSec
force-pushed
the
use-aes256-memberlist-encryption
branch
from
5e3c790 to
72cce25
Compare
Signed-off-by: AzraelSec <me@azraelsec.sh>
|
Thanks, queued for merging! |
|
Happy to contribute! Thanks 😄 |
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.
SpeakerListcurrently configures memberlist to use AES-128 to encrypt the messages involved in the cluster membership management. This PR increases the size ofSecretKeyto make memberlist use AES-256 instead.Closes #1982.