trezor emulator: can't set up the device

[danielabrozzoni]

Hey,
I'm trying to set up a trezor emulator using this command:

❯ hwi --device-type trezor -i setup

The emulator prompts me with a "Enter new pin" screen and, immediately after, hwi returns this error:

❯ hwi --device-type trezor -i setup                           
{"error": "PIN requested but no sequence was configured", "code": -13}

If I try to enter the new PIN in the emulator, it freezes.

Any idea how to solve this?

I'm using hwi 2.1.1 and trezor-firmware on commit 4e800b6ffde97862026c6196f7d983d62a05ea71

[prusnak]

I'm using hwi 2.1.1 and trezor-firmware on commit 4e800b6ffde97862026c6196f7d983d62a05ea71

Can you try HWI from master and trezor-firmware from master?

[danielabrozzoni]

I'm hitting the same problem on hwi master (857e935) and on trezor-firmware master (trezor/trezor-firmware@4528577)

[prusnak]

@matejcik can you have a look?

[matejcik]

The error message seems to be coming out of debuglink. Looks like HWI is setting up TrezorClientDebugLink for the client instance, which wants to enter the PIN for you, except there is no PIN preconfigured.

In your usecase I presume hwi should be using regular TrezorClient instead of TrezorClientDebugLink.

[danielabrozzoni]

Thanks for looking into it!

Btw, I just noticed that I hit the same bug when using restore, I assume the fix will be similar to the fix for setup - but I can create a different issue if that's not the case

[prusnak]

@danielabrozzoni does this commit help with the issue? prusnak@80b13fb

[danielabrozzoni]

Yep, both restore and setup are fixed there

[prusnak]

@achow101 Why do you use TrezorClientDebugLink for communicating with the emulator? It does seems strange ...

[prusnak]

ISTM that these two commits are better way how to implement things?

prusnak@80b13fb
+
prusnak@eb263e3

(both in branch https://github.com/prusnak/HWI/tree/trezor-remove-debuglink)

Or is there something I am missing?

[achow101]

Why do you use TrezorClientDebugLink for communicating with the emulator? It does seems strange ...

So that the tests can provide the pin and passphrase programatically.

[prusnak]

So that the tests can provide the pin and passphrase programatically.

I think we should update the code in a way that TrezorClientDebugLink is only used from tests and in production we only use TrezorClient (which is imported as Trezor because of the naming conflict).