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
128+0 records in
128+0 records out
128 bytes copied, 0.0003931 s, 326 kB/s
128+0 records in
128+0 records out
128 bytes copied, 0.000358158 s, 357 kB/s
$ sha256sum *.zeroed build/core-T3T1{,-bitcoinonly}/firmware/firmware.bin | sort
We surmise that the header size for the Trezor Safe 5 may be different which have lead to different values:
Greetings team Trezor! 😊
Danny here from walletscrutiny
Describe the bug
Firmware version and revision
2.8.3
Desktop/smartphone setup (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
1. We begin by downloading the latest binary from trezor.
2. We get the hashes for the binaries.
3. We then proceed with building
The results:
4. We then begin the process for signature zeroing. We have tried several variations, based on this closed GitHub issue.
Then:
We surmise that the header size for the Trezor Safe 5 may be different which have lead to different values:
After several different results, we ran diffoscope:
For the 'regular' and 'bitcoin-only' binaries:
The results:
diffoscope_results_bitcoinonly.txt
diffoscope_results_regular.txt
Expected behavior
Hashes should match.
Screenshots
n/a
Additional context
Requesting documentation changes to this page to include Trezor Safe 5.
https://github.com/trezor/trezor-firmware/blob/main/docs/common/reproducible-build.md
The text was updated successfully, but these errors were encountered: