Skip to content
This repository was archived by the owner on Apr 12, 2022. It is now read-only.

WARNING: Trezor not ready #13

Open
drewdotpro opened this issue Nov 12, 2018 · 8 comments
Open

WARNING: Trezor not ready #13

drewdotpro opened this issue Nov 12, 2018 · 8 comments

Comments

@drewdotpro
Copy link

Trezor One, Firmware version 1.7.1

I had been previously able to use trezor-ssh-agent, but since I last used it I have:
Restarted the PC
Updated my Trezor Firmware

The Trezor works fine on the wallet website, but when using the app and selecting 'Show Public Key' I received the message 'Trezor not ready'.

Steps for recreation:

  • Chrome not running
  • Trezor connected and showing logo
  • Start trezor-ssh-agent
  • Right click, choose 'Show Public Key'

Log:

[12.11.2018 09:31:45] INFO: Java version: 1.8.0_191-b12 (32-bit)
[12.11.2018 09:31:45] INFO: Java home: C:\Program Files (x86)\Java\jre1.8.0_191
[12.11.2018 09:31:45] INFO: Trezor SSH Agent 1.0.3 started successfully
[12.11.2018 09:31:45] INFO: Existing settings file loaded: C:\Users\drew\Trezor_Agent.properties
[12.11.2018 09:31:45] INFO: Trezor Service Started
[12.11.2018 09:31:45] INFO: Received USB event: SHOW_DEVICE_DETACHED
[12.11.2018 09:31:49] INFO: Request for operation: SSH2_AGENT_GET_IDENTITIES
[12.11.2018 09:31:49] WARNING: Trezor not ready.
@drewdotpro
Copy link
Author

Let me know if I can provide any extra information please, as I have not found a solution.

@antonio-fr
Copy link

Probably related to this latest Trezor One firmware update :
"Trezor One new firmware version 1.7.1 adds the support of WebUSB for both Trezor Wallet and Trezor Password Manager (TPM). These changes allow users of Google Chrome to connect to Trezor Wallet and TPM directly, without the use of Trezor Bridge."
This minor version update was not suppose to change the communication protocol and break compatibility, but who knows what they can break up.

@prusnak
Copy link

prusnak commented Dec 20, 2018

Versions 1.7.0 and newer communicate via WebUSB protocol (almost identical to HID used previously). Also the vendor_id and product_id has changed to 0x1209 and 0x53C1 respectively to match Trezor Model T (also using WebUSB).

@antonio-fr
Copy link

I did a fork of the 1.7.x firmware versions which is still using HID usb. So this app keeps running on an updated Trezor One.
https://github.com/antonio-fr/trezor-mcu-hid

@drewdotpro
Copy link
Author

This is great, can you raise a PR to get that change merged here, and hopefully repo maintainer can review, merge, and build a release?

@antonio-fr
Copy link

I don't get your query. To be clear, I didn't fork this project. This agent can't run on an official Trezor update. Still, since Trezor team shattered retro-compatibility, I forked the firmware of the Trezor to keep retro-compatibility. This way, you can run this agent app on an updated Trezor, using the alternative "HID" firmware (see the binaries in trezor-mcu-hid/releases/tag/v1.7.3.

About this project, it downloads this JAR for communicating with the Trezor, and I haven't found any source for this dependecy. So the modification for this matter is not inside this agent project (only increment the POM file), but I don't know where this can be done.

@drewdotpro
Copy link
Author

Oh sorry I misunderstood your comment, and replied without following the link. I see you've made custom firmware for the Trezor One so it's compatible with this repo. Nice work.

As a personal preference I'll never use non-official firmware on my Trezor devices, so I hope @martin-lizner updates this repo to be compatible with the official firmware.

@thossoma
Copy link

I second this...would like to use the Trezor Model T as fully advertised. I use windows machines primarily and wanted to utilize this as my SSH Key. Pretty disappointed that I can't.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants