Fix default ivLength in dump-db tool #947
Open
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.
The
dump-db
tool appears to be designed for a much older version of Trilium.Related issue:
zadam/trilium#3017
Referencing this commit:
Commit Reference
At that time, the
ivLength
was incorrectly set to 13 instead of the correct value of 16. Consequently, if you attempt to use this tool to decrypt encrypted notes from the current database version, you will encounter errors because the tool's defaultivLength
remains at 13.Code reference:
Source Code Reference
Error message:
Caught WRONG_FINAL_BLOCK_LENGTH, returning cipherText instead
To reproduce the issue, you can use the following test code:
To resolve this issue and ensure compatibility with the current database, the
ivLength
should be updated to a default value of 16.