-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
👑 Private keys import and accounts backup #3089
Conversation
Handle importing wallets with private key in the keyring service: * save pk imported accounts in the encrypted vault * handle serialization and deserialization of pk imported wallets * handle siging messages with both keyrings and single wallets * fix types and field names in the redux store
* add redux method for pk wallets import * rename `getKeyringSourceForAddress` to `getSignerSourceForAddress` * ensure addresses are normalized
* add unit tests for keyring service * move existing tests to keyring service folder * add utils for local storage mocking
* add unit tests for each type of signing transactions * add new test utils * remove some duplicated unit tests
Make separate import seed form component to allow private key import page to reuse the same page layout.
Add page, new icons and link to the private key page on tabbed onboarding flow.
Btw this will be enforced by GitHub, as long as the target branch is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some higher-level architectural thoughts on how to reconsider the addition of new methods and redux actions by instead adding new variants to the existing data structures, and reconsidering private keys as “simple” keyrings with only one key and no derivation capabilities.
background/services/keyring/index.ts
Outdated
hiddenAccounts: { [address: HexString]: boolean } | ||
} | ||
|
||
interface Events extends ServiceLifecycleEvents { | ||
locked: boolean | ||
keyrings: { | ||
wallets: WalletData[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why add this if WalletData
(naming aside) conforms to Keyring
, the type carried by the keyrings
field?
In many ways it's useful to treat a private key as a keyring with only one key. Particularly if we distinguish an HDKeyringAccountSigner
from a KeyringAccountSigner
, and make address derivation available only to an HDKeyringAccountSigner
, I think we continue to drive towards a simpler API surface.
- create single import method to import both HD wallets and pk wallets - rename `wallets` to `privateKeys`
Moving this to draft for now, will notify when it is ready. |
Closes #3468 ## What When users try to copy a recovery phrase/private key we should warn them that it's not safe to do so. ## UI https://github.com/tahowallet/extension/assets/23117945/ce1d143e-58ef-4f23-bad8-e1b355954a9d ## Testing - [x] Try to copy a recovery phrase/private key, warning should warn that it's not safe to do. - [x] Check the "Don’t ask me again" option. The warning should not be displayed again. Latest build: [extension-builds-3488](https://github.com/tahowallet/extension/suites/13780837887/artifacts/763854812) (as of Thu, 22 Jun 2023 06:03:38 GMT).
Closes #3471 Adds a dropdown on settings to allow changing the maximum amount of time the wallet can remain idle before locking signing. This new setting is updated through an async thunk which triggers an event to also handle the change on the keyring service. The data is persisted on preferences db and exposed through redux to the UI. ## Testing Env ``` SUPPORT_CUSTOM_AUTOLOCK=true ``` ## To Test - [x] Import an account - [x] Lock and unlock your wallet - [x] Head to settings, change auto-lock time - [x] Change your system's date or change the options [here](https://github.com/tahowallet/extension/blob/be6fae78bd7949cd5e4d8f37c882152d00e8141d/ui/pages/Settings.tsx#L308), test that different time options work correctly - [x] If the wallet has been idle for 10 minutes and the current auto lock setting changes to from 15 minutes to 5, the wallet should lock itself. Latest build: [extension-builds-3477](https://github.com/tahowallet/extension/suites/13795656037/artifacts/764974743) (as of Thu, 22 Jun 2023 16:11:15 GMT).
- add required packages - configure webpack to work with webAssembly - add neccessary config to `content_security_policy` to allow webAssembly
Let's set length to 32 bytes to match length expected by AES-GCM
Catch erros if vaults migration to Argon2 fails and allow to continue with old vaults encrypted with PBKDF2. Log analytics event when vaults are succesfully migrated.
- allowed Jest to fetch WebAssembly files - moved `crypto.subtle` mock to global setup
- for Jest to work with WebAssembly we need to update to next major version - to support dependencies for new Jest version we need to bump Typesript as well - let's fix problems found by new Typescript version
Allow destructuring objects to remove unwanted fields from the objects. This is pattern we are using often across the codebase.
- return `success` boolean - make sure decrypted vaults match - send event on migration fail
Vault migration is no longer tracked as Argon2 specifically, but generically for all migrations. Already-migrated vaults are not tracked, and the migration function return value reflects that no migration was performed. Additionally, error messages are bubbled out of the migration function and reported up to the caller. The main outcome here is that PostHog migration events include the migrated-to version, and PostHog migration failure events include the error message. This will leave us open to future migrations, and will let us know if there are certain failures that are happening broadly that we may be able to do something about. Notably, wrong passwords will be tracked as migration errors if a wrong password is typed with an older vault version in the mix. Mitigating this may or may not be a good idea.
Resolves #3470 ### What Let's use Argon2 instead of PBKDF2 🔑 What was already done: - [x] added required packages - [x] configured webpack config to work with webAssembly following [example from the docs](https://github.com/antelle/argon2-browser/tree/master/examples/webpack) - [x] add necessary config to `content_security_policy` to allow webAssembly - without `'wasm-eval'` we are not able to use argon implementation in the extension - [x] migration from old vaults to new vaults - [x] handling errors during migration and allowing users to continue with old implementation if needed - [x] added one time analytics event after successful migration - [x] updated Jest to allow unit tests to work with WebAssembly, updated Typescript as this was necessary to make new version of Jest work correctly and fixed a bunch of Typescript issues - most fixes are copied from #3415 ### Testing - [x] test migration from main - install extension on `main`, add some HD wallets, checkout this branch, reload and unlock the wallet, make sure you don't see the error about failed migration in the background console, check if analytics event has been emitted, lock and unlock more than one time - [x] install extension on this branch, test locking and unlocking the wallet - [x] try to make webassembly part break (throw Error [here](https://github.com/tahowallet/extension/blob/migrate-to-argon/background/services/internal-signer/encryption.ts#L118)) and make sure user is able to continue with old vaults Latest build: [extension-builds-3502](https://github.com/tahowallet/extension/suites/14011994578/artifacts/782054890) (as of Sun, 02 Jul 2023 21:28:25 GMT).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All righty, we are good to go here. Waiting on one more round of thoughts from the auditors and then we're going to land this puppy with great fanfare.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is time 🏆
## What's Changed * Add private key onboarding flow by @jagodarybacka in #3119 * Private key JSON import by @jagodarybacka in #3177 * Allow export of private keys and mnemonics by @jagodarybacka in #3248 * Export private key form by @jagodarybacka in #3255 * Unlock screen for the account backup by @kkosiorowska in #3257 * Show mnemonic menu by @jagodarybacka in #3259 * Fix background blur issue by @jagodarybacka in #3265 * Account backup UI fixes by @jagodarybacka in #3270 * Fix unhiding removed accounts by @jagodarybacka in #3282 * New error for incorrectly decrypted JSON file by @jagodarybacka in #3293 * Export private keys from HD wallet addresses by @jagodarybacka in #3253 * Refactor keyring redux slice to remove `importing` field by @jagodarybacka in #3309 * 📚 Accounts backup by @kkosiorowska in #3252 * Catch Enter keypress on Unlock screen by @jagodarybacka in #3355 * Rename `keyring` to `internal signer` and other improvements by @jagodarybacka in #3331 * 🗝 QA - Accounts backup and private key import by @jagodarybacka in #3266 * Remove private key signers if they are replaced by accounts from HD wallet by @jagodarybacka in #3377 * RFB 4: One-Off Keyring Design by @Shadowfiend in #3372 * Copy to clipboard warning by @kkosiorowska in #3488 * Allow setting custom auto-lock timer by @hyphenized in #3477 * Use Argon2 for encrypted vaults by @jagodarybacka in #3502 * 👑 Private keys import and accounts backup by @jagodarybacka in #3089 * Untrusted assets should not block the addition of custom tokens by @kkosiorowska in #3491 * Flip updated dApp connections flag by @Shadowfiend in #3492 * v0.41.0 by @Shadowfiend in #3531 * Switch to a given network if adding a network that is already added. by @0xDaedalus in #3154 * Remove waiting for Loading Doggo component in E2E tests by @jagodarybacka in #3541 * Squeeze content to better fit on Swaps page by @jagodarybacka in #3542 * Refactor of terms for verified/unverified assets by @kkosiorowska in #3528 * Fix ChainList styling by @fulldecent in #3547 * Update release checklist by @jagodarybacka in #3548 * Fix custom asset price fetching by @hyphenized in #3508 * Sticky Defaults: Make Taho-as-default replace MetaMask in almost all cases by @Shadowfiend in #3546 ## New Contributors * @fulldecent made their first contribution in #3547 **Full Changelog**: v0.41.0...v0.42.0 Latest build: [extension-builds-3549](https://github.com/tahowallet/extension/suites/14268975651/artifacts/801826435) (as of Thu, 13 Jul 2023 09:51:56 GMT).
About this PR
This PR will contain all changes for features:
Initial scope
Resolves #3070
What
Handle importing wallets with private keys in the keyring service:
Cleanup and add more tests:
factories
Testing
Latest build: extension-builds-3089 (as of Thu, 06 Jul 2023 12:56:07 GMT).