You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 16, 2019. It is now read-only.
The communication protocol changed unexpectedly in firmware 1.7.1.
Can you share details or point to the relevant documentation of what what changed in the communication protocol of the Trezor (Model One) in the firmware version 1.7.1 ?
There were some changes that break some unmaintained software. Any details about the change can help others developers to make it work again. See : martin-lizner/trezor-ssh-agent#13
This issue is mostly to get help about the issue regarding this other software. One need at least some detailed information about the change of the behavior since the 1.7.1 firmware.
The text was updated successfully, but these errors were encountered:
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).
Packet format and everything else hasn't changed at all.
Since 1.7 broke retro-compatibility of the apps using a Trezor One, even the vendor ID changed, I did a new fork of this firmware dedicated to maintain HID and full retro-compatibility about the USB link. https://github.com/antonio-fr/trezor-mcu-hid
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The communication protocol changed unexpectedly in firmware 1.7.1.
Can you share details or point to the relevant documentation of what what changed in the communication protocol of the Trezor (Model One) in the firmware version 1.7.1 ?
There were some changes that break some unmaintained software. Any details about the change can help others developers to make it work again. See : martin-lizner/trezor-ssh-agent#13
This issue is mostly to get help about the issue regarding this other software. One need at least some detailed information about the change of the behavior since the 1.7.1 firmware.
The text was updated successfully, but these errors were encountered: