Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
store encryption key with Android's keystore
See original GitHub issueIf I’m not mistaken, BlueWallet on Android does NOT use Android’s KeyStore to store the wallet’s encryption key, but derives an encryption key from the wallet passphrase that is then used to decrypt the wallet. Is my understanding correct?
If this is the case, then I strongly suggest that the encryption key should be stored with Android’s KeyStore, which is backed by hardware security for many Android devices and is thus significantly harder to extract or bruteforce than the software key derivation (which can be performed via an offline attack on much more powerful hardware after getting hold of the encrypted wallet).
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
if youre intereted, transaction data (which contains no secrets) is offloaded to Realm database (that’s faster) and this tx data is encrypted via the same user’s password or default password. all encryption is AES256.
That is correct. The file class/app-storage.js is where this takes place.