Repository navigation
RFC: move encryption type to aes256gcm - #83
Draft
AndrewJackson2020 wants to merge 1 commit into
Draft
AndrewJackson2020 wants to merge 1 commit into
AndrewJackson2020 wants to merge 1 commit into
Conversation
AndrewJackson2020
force-pushed
the
change_to_aes_256_gcm
branch
from
November 10, 2026 21:19
b52379a to
bf866f4
Compare
AndrewJackson2020
changed the title
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.
Currently we are use xchcha20 encryption. Per the libsodium documentation[0]:
Given that it is not a formally specified cypher it probably makes sense to move to aes256gcm which is formally specified and NIST approve [1,2]
[0] https://libsodium.gitbook.io/doc/advanced/stream_ciphers/xchacha20
[1] https://csrc.nist.gov/Projects/block-cipher-techniques
[2] https://csrc.nist.gov/pubs/sp/800/38/d/final