Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Firmware 2.3.1 cannot sign arbitrary paths #1255

Closed
cantilope opened this issue Sep 12, 2020 · 1 comment
Closed

Firmware 2.3.1 cannot sign arbitrary paths #1255

cantilope opened this issue Sep 12, 2020 · 1 comment
Labels
bug Something isn't working as expected

Comments

@cantilope
Copy link

In versions 2.3.0 and prior with Electrum, it was possible to sign arbitrary paths. For example a segwit Bitcoin wallet with m/84'/9999'/0'/0/0. Since firmware 2.3.1, the trezor device returns "Forbidden key path". As a result the Trezor can no longer be used with wallets that use arbitrary paths. I am using Electrum 4.0.3 and can confirm I am able to sign a transaction with firmware 2.3.0 but not 2.3.1.

@cantilope cantilope added the bug Something isn't working as expected label Sep 12, 2020
@prusnak
Copy link
Member

prusnak commented Sep 12, 2020

  1. always use the latest firmware (which is 2.3.3 at the moment, not 2.3.1)
  2. you can turn off this safety checks via trezorctl set safety-checks prompt (make sure you have the latest python-trezor 0.12.2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected
Projects
None yet
Development

No branches or pull requests

2 participants