Repository navigation
docs: Document the file format used by the server - #649
Merged
Merged
Conversation
📊 Code Coverage Report
Coverage report generated by cargo-tarpaulin |
ueno
approved these changes
Nov 11, 2026
| //! | ||
| //! The key is derived from the password with PBKDF2-HMAC-SHA256, using at | ||
| //! least 100000 iterations and a 32 bytes salt. Items are encrypted with | ||
| //! AES-128-CBC, with PKCS#7 padding and a random IV, and the same key is used |
Contributor
There was a problem hiding this comment.
I misremember it was AES-256-CBC, but yes, this looks correct. That means we might want to update it to AES-256-CBC and SHA384 or SHA512 at some point to be compliant with CNSA 2.0 (i.e., PQC).
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.
cc @ueno