feat: introduce encryption result version #48
Closed
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 PR introduces a
version
property in theEncryptionResult
object. Adding a version to the encryption result object allows the use of different decryption algorithms or configurations based on it.The current implementation (prior to this PR) is classified as version
1.0
, and forEncryptionResult
objects that don't have aversion
property at all, version 1.0 is inferred: this ensures that the decryption methods of this library can still decrypt old versions.Moreover, this PR also adds a
2.0
version, where the encryption key is derived with increased iterations.When encrypting, it is now possible to specify the version (defaults to
2.0
).Changes
iterations
optional argument tokeyFromPassword
with600000
as default valueversion
argument toencryptWithDetail
with2.0
as the default valueversion
argument toencryptWithKey
with2.0
as the default value