mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-23 18:41:38 +01:00
1880cda9b9
This is only a bug in dev, but was committed yesterday. Sometimes the `encrypt` method was being passed values other than the password as the encryption key, leading to un-unlockable vaults. To find this, and avoid it for all time hereafter, I added several more steps to our oft-neglected integration test suite, which now fully initializes a vault, locks it, and unlocks it again, to make sure all of those steps definitely work always. |
||
|---|---|---|
| .. | ||
| auto-faucet.js | ||
| auto-reload.js | ||
| config-manager.js | ||
| encryptor.js | ||
| extension-instance.js | ||
| extension.js | ||
| id-management.js | ||
| idStore-migrator.js | ||
| idStore.js | ||
| inpage-provider.js | ||
| is-popup-or-notification.js | ||
| message-manager.js | ||
| migrations.js | ||
| nodeify.js | ||
| notifications.js | ||
| obj-multiplex.js | ||
| port-stream.js | ||
| random-id.js | ||
| remote-store.js | ||
| sig-util.js | ||
| stream-utils.js | ||