arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-12-22 22:38:08 +00:00
Code Issues Releases Wiki Activity

update readme to reflect new mytrezor location

Browse Source
This commit is contained in:
Pavol Rusnak 2016-07-04 19:03:27 +02:00
parent 437c5739f1
commit b95f785701
No known key found for this signature in database
GPG Key ID: 91F3B339B9A02A3D
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -24,11 +24,10 @@ This creates file `output/bootloader.bin` and prints its fingerprint and size at
## How to get fingerprint of firmware signed and distributed by SatoshiLabs? ## How to get fingerprint of firmware signed and distributed by SatoshiLabs?
1. Pick version of firmware binary listed on https://mytrezor.com/data/firmware/releases.json 1. Pick version of firmware binary listed on https://wallet.mytrezor.com/data/firmware/releases.json
2. Download it: `wget -O trezor.signed.bin.hex https://mytrezor.com/data/firmware/trezor-1.1.0.bin.hex` 2. Download it: `wget -O trezor.signed.bin https://wallet.mytrezor.com/data/firmware/trezor-1.3.6.bin`
3. `xxd -r -p trezor.signed.bin.hex trezor.signed.bin` 3. `./firmware-fingerprint.sh trezor.signed.bin`
4. `./firmware-fingerprint.sh trezor.signed.bin`
Step 4 should produce the same sha256 fingerprint like your local build (for the same version tag). Step 3 should produce the same sha256 fingerprint like your local build (for the same version tag).
The reasoning for `firmware-fingerprint.sh` script is that signed firmware has special header holding signatures themselves, which must be avoided while calculating the fingerprint. The reasoning for `firmware-fingerprint.sh` script is that signed firmware has special header holding signatures themselves, which must be avoided while calculating the fingerprint.