mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-12-23 01:39:44 +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. |
||
|---|---|---|
| .. | ||
| accounts | ||
| components | ||
| css | ||
| first-time | ||
| img | ||
| keychains/hd | ||
| reducers | ||
| account-detail.js | ||
| actions.js | ||
| app.js | ||
| conf-tx.js | ||
| config.js | ||
| conversion.json | ||
| info.js | ||
| new-keychain.js | ||
| reducers.js | ||
| root.js | ||
| send.js | ||
| settings.js | ||
| store.js | ||
| template.js | ||
| unlock.js | ||
| util.js | ||