fix(NOTIFY-1190): key generation bug for react native scrypt #4755
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.
Explanation
This PR fixes a bug where we passed a
string
parameter instead of aUInt8Array
to the react nativescrypt
function.This resulted in faulty key generation, bugs in encryption / decryption, and inconsistencies between mobile and the other clients.
References
https://consensyssoftware.atlassian.net/browse/NOTIFY-1190
Changelog
@metamask/profile-sync-controller
UInt8Array
instead ofstring
for the password argument ofnativeScryptCrypto
Checklist