arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-15 20:19:23 +00:00
Code Issues Releases Wiki Activity
259 Commits 341 Branches 206 Tags 195 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
a0571e02a7
Go to file
Jochen Hoenicke a0571e02a7 Removed more magic numbers. 
`KEY_PATH_LEN`: length of the derivation path in the key handle

`KEY_PATH_ENTRIES`: number of entries in derivation path including
initial BIP-43 selector.

`KEY_HANDLE_LEN`: length of key handle (derivation path + HMAC checksum)
2016-05-18 03:05:04 +02:00
bootloader use __asm__ instead of asm 2016-04-29 16:10:41 +02:00
demo fix demo 2016-05-16 16:41:09 +02:00
firmware Removed more magic numbers. 2016-05-18 03:05:04 +02:00
gen move submodules to vendor subdirectory 2015-12-15 23:01:54 +01:00
gitian add gitian build (work in progress) 2016-01-19 21:15:39 +01:00
vendor use MEMSET_BZERO and U2F_APPID_SIZE macros 2016-05-16 18:18:21 +02:00
.gitignore bootloader source code 2014-10-23 18:09:41 +02:00
.gitmodules move submodules to vendor subdirectory 2015-12-15 23:01:54 +01:00
.travis.yml fix travis build 2015-12-15 23:22:42 +01:00
bootloader-docker-build.sh use OPTFLAGS=-Os for bootloader docker build 2016-02-29 13:33:55 +01: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 use the latest ubuntu lts in docker build 2016-05-08 14:26:21 +02:00
firmware-docker-build.sh bootloader autobuild in docker 2016-02-29 13:25:54 +01:00
firmware-fingerprint.sh prepare 1.2.0 release 2014-07-03 01:20:34 +02:00
layout.c call layout functions where needed to rewrite the display after dialog choice 2015-02-25 17:57:47 +01:00
layout.h rework layoutProgress functions 2014-12-21 18:58:56 +01:00
Makefile add make vendor 2016-05-11 14:38:04 +02:00
Makefile.include use MEMSET_BZERO and U2F_APPID_SIZE macros 2016-05-16 18:18:21 +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 use hdnode_private_ckd_cached where appropriate 2015-01-26 20:24:07 +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 cleanup oledDrawChar code 2015-11-18 23:35:28 +01:00
oled.h cleanup oledDrawChar code 2015-11-18 23:35:28 +01:00
README.md update readme 2016-05-11 21:07:56 +02: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 enable stack protector 2014-07-31 19:44:03 +02:00
serialno.h import v1.0.0 2014-04-29 14:38:32 +02:00
setup.c move submodules to vendor subdirectory 2015-12-15 23:01:54 +01:00
setup.h move APPVER guards from includes to app code 2014-07-07 15:03:34 +02: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

http://bitcointrezor.com/

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://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 (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.