Solution: Encryption code is obsolete and supports only Blowfish/SHA1 #339
Conversation
This file contains 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
… obsolete and supports only Blowfish/SHA1. It is now possible to save files with the old Blowfish encryption as well as with the AES256-CBC encryption. By default, the data is stored with AES256 CBC encryption. Only files that still have the old encryption are still saved with this encryption. resolves tdf#162
mistmist
approved these changes
Nov 28, 2024
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.
This pull request fixes the issue #162 that the encryption code is obsolete and supports only Blowfish/SHA1.
It is now possible to save files with the old Blowfish encryption as well as with the AES256-CBC encryption.
By default, the data is stored with AES256 CBC encryption. Only files that still have the old encryption are still saved with this encryption.
resolves #162