arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2025-02-22 12:32:02 +00:00
Code Issues Releases Wiki Activity
386 Commits 408 Branches 211 Tags 213 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
0b51d060d8
Go to file
Saleem Rashid 0b51d060d8
allow ClearSession purely via confirm button 
Holding confirm button at home screen asks user whether they wish to
lock the TREZOR (clear the cached PIN and passphrase and show the
screensaver). This is identical behaviour to the ClearSession message.
2016-10-25 15:21:56 +02:00
bootloader add checking of buttons to bootloader 2016-10-06 15:03:11 +02:00
demo remove DialogIcon enum, use bitmap structure directly 2016-06-08 19:20:07 +02:00
firmware allow ClearSession purely via confirm button 2016-10-25 15:21:56 +02:00
gen add gitlab to u2f_knownapps 2016-07-04 15:48:36 +02:00
gitian add gitian build (work in progress) 2016-01-19 21:15:39 +01:00
vendor update trezor-crypto 2016-10-24 20:55:45 +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 failure 2016-05-28 19:49:31 +02: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 fix ar usage 2016-05-24 20:27:45 +02:00
Makefile.include Use trezor-crypto ECDH, adding Curve25519 support 2016-10-16 01:34:02 +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 Faster SPI communication 2016-08-26 18:43:16 +02:00
oled.h cleanup oledDrawChar code 2015-11-18 23:35:28 +01:00
README.md update readme to reflect new mytrezor location 2016-07-04 19:04:13 +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 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 Faster SPI communication 2016-08-26 18:43:16 +02: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://wallet.mytrezor.com/data/firmware/releases.json
  2. Download it: wget -O trezor.signed.bin https://wallet.mytrezor.com/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.