arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-22 23:48:12 +00:00
Code Issues Releases Wiki Activity
442 Commits 353 Branches 205 Tags 210 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
49645ba277
Go to file
Jochen Hoenicke 49645ba277 Compute hash before checking signatures. (#158) 
This fixes the problem where an invalid hash is shown, if
the firmware contains no signing key indices.
2017-03-30 02:24:53 +02:00
bootloader Compute hash before checking signatures. (#158) 2017-03-30 02:24:53 +02:00
demo fix usage of RNG before setup (#150/#151) 2017-02-17 13:19:05 +01:00
firmware update trezor-crypto 2017-03-28 23:19:59 +02:00
gen adapt python scripts to Python3 2017-02-01 18:07:47 +01:00
gitian add gitian build (work in progress) 2016-01-19 21:15:39 +01:00
vendor update trezor-crypto 2017-03-28 23:19:59 +02:00
.gitignore add _attic to gitignore 2017-01-24 15:19:15 +01:00
.gitmodules move submodules to vendor subdirectory 2015-12-15 23:01:54 +01:00
.travis.yml add webhooks to travis 2016-11-23 11:50:14 +01:00
bootloader-docker-build.sh add set -e to shell scripts 2016-07-03 13:54:32 +02:00
buttons.c import v1.0.0 2014-04-29 14:38:32 +02:00
buttons.h cleanup oledDrawChar code 2015-11-18 23:35:28 +01:00
COPYING import v1.0.0 2014-04-29 14:38:32 +02:00
Dockerfile add python-ecdsa dependency 2016-07-23 10:06:19 +02:00
firmware-docker-build.sh sign firmware inside docker container 2016-08-29 19:20:50 +02:00
firmware-fingerprint.sh add set -e to shell scripts 2016-07-03 13:54:32 +02:00
layout.c remove DialogIcon enum, use bitmap structure directly 2016-06-08 19:20:07 +02:00
layout.h remove DialogIcon enum, use bitmap structure directly 2016-06-08 19:20:07 +02:00
Makefile timer: Use Cortex-M3 SysTick timers 2016-11-17 02:07:46 +01:00
Makefile.include update trezor-crypto 2017-03-28 23:19:59 +02:00
memory_app_0.0.0.ld import v1.0.0 2014-04-29 14:38:32 +02:00
memory_app_1.0.0.ld import v1.0.0 2014-04-29 14:38:32 +02:00
memory.c memory protection: do not write reserved bits (#138) 2017-01-26 16:07:45 +01:00
memory.h import v1.0.0 2014-04-29 14:38:32 +02:00
memory.ld import v1.0.0 2014-04-29 14:38:32 +02:00
oled.c fix when oled triangle is shown 2017-01-19 16:16:57 +01:00
oled.h fix when oled triangle is shown 2017-01-19 16:16:57 +01:00
README.md update readme 2017-01-10 15:14:29 +01:00
rng.c use Knuth shuffles 2015-02-13 20:51:02 +01:00
rng.h use Knuth shuffles 2015-02-13 20:51:02 +01:00
serialno.c fix unaligned access in serialno; update trezor-crypto 2016-08-29 22:37:27 +02:00
serialno.h import v1.0.0 2014-04-29 14:38:32 +02:00
setup.c fix usage of RNG before setup (#150/#151) 2017-02-17 13:19:05 +01:00
setup.h move APPVER guards from includes to app code 2014-07-07 15:03:34 +02:00
timer.c timer: Fix non-critical integer overflow (#129) 2016-11-23 20:22:28 +01:00
timer.h timer: Fix non-critical integer overflow (#129) 2016-11-23 20:22:28 +01:00
util.c import v1.0.0 2014-04-29 14:38:32 +02:00
util.h fix usage of inline/static 2016-02-15 15:29:19 +01:00

README.md

TREZOR Firmware

Build Status gitter

https://trezor.io/

How to build TREZOR firmware?

  1. Install Docker
  2. git clone https://github.com/trezor/trezor-mcu.git
  3. cd trezor-mcu
  4. ./firmware-docker-build.sh TAG (where TAG is v1.3.2 for example, if left blank the script builds latest commit)

This creates file output/trezor-TAG.bin and prints its fingerprint at the last line of the build log.

How to build TREZOR bootloader?

  1. Install Docker
  2. git clone https://github.com/trezor/trezor-mcu.git
  3. cd trezor-mcu
  4. ./bootloader-docker-build.sh

This creates file output/bootloader.bin and prints its fingerprint and size at the last line of the build log.

How to get fingerprint of firmware signed and distributed by SatoshiLabs?

  1. Pick version of firmware binary listed on https://wallet.trezor.io/data/firmware/releases.json
  2. Download it: wget -O trezor.signed.bin https://wallet.trezor.io/data/firmware/trezor-1.3.6.bin
  3. ./firmware-fingerprint.sh trezor.signed.bin

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.