arno
/
trezor-firmware
mirror of https://github.com/trezor/trezor-firmware.git
1
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e9fd756daa'
${ noResults }
trezor-firmware/README

25 lines
1.0 KiB
Raw Normal View History Unescape

Howto for deterministic builds
10 years ago
TREZOR firmware
import v1.0.0
10 years ago
http://bitcointrezor.com/
Howto for deterministic builds
10 years ago
How to build Trezor firmware?
=============================
1. Install Docker (docker.com)
2. git clone git@github.com:trezor/trezor-mcu.git
3. cd trezor-mcu
4. ./firmware-docker-build.sh
This generates trezor.bin in current directory and prints sha256 fingerprint on last line of build log.
How to get sha256 fingerprint of firmware signed and distributed by SatoshiLabs?
================================================================================
1. Pick proper version of firmware binary listed on https://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
3. xxd -r -p trezor.signed.bin.hex trezor.signed.bin
4. ./firmware-fingerprint.sh trezor.signed.bin
Step 4 should produce the same sha256 fingerprint like your local build.
The reasoning behind "firmware-fingerprint.sh" is that signed firmware has special header holding signatures themselves,
which must be removed before calculating fingerprint.