Update @metamask/browser-passworder
#62
Merged
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
mikesposito
force-pushed
the
chore/bump-browser-passworder
branch
from
5c893a7
to
cc69d9b
Compare
legobeat
approved these changes
Dec 12, 2023
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.
Vault updated with a version >4.1.0 of
@metamask/browser-passworderare encrypted with a key derived with different iterations based on the client's wish.This means that currently, the
vault-decryptortool might not be able to decrypt new vaults, as the key will most likely be derived with the wrong number of iterations.This PR updates
@metamask/browser-passworderto^4.3.0, making decryption of new vaults possibleFixes #61