Add simulator device #452
Open
Add simulator device #452
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This simulator is fully compatible with a Trezor device, but takes the mnemonic/passphrase via commandline or pinentry. Can be useful for testing, try-before-you-buy for hardware devices (in the context of trezor-agent only), and CI. For the latter, is an improvement over FakeDevice, in that it can produce different keys based on derivation path, so it can be used to test things like original vs foreign key detection based on derivation from user id, which FakeDevice can't do.
And it's also good for producing doc examples that aren't based on anyone's real key.
Also adds the ability to have per-device command line arguments for all tools. Currently used for simulator mnemonics. But can also be used for e.g. Trezor multi-device selection.
Also fixes an issue that the passphrase caching made "Re-enter encryption:" prompt meaningless, since it would immediately pull the previous entry from cache.