Skip to content
🔒 Trezor Firmware Monorepo
C Python C++ Makefile Assembly Objective-C Other
Branch: master
Clone or download
Latest commit b5446bd Feb 17, 2020
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/ISSUE_TEMPLATE github: update issue templates Dec 3, 2019
ci ci: ensure system Python 3.7 is used even if other pythons are available Feb 11, 2020
common all: do not send state in PassphraseAck (not needed for compatibility) Feb 13, 2020
core core/emulator: properly ignore inotify problems (fixes #854) Feb 17, 2020
crypto crypto: fix last commit Feb 17, 2020
docs docs/common: add links and fix some typos Feb 12, 2020
legacy all: do not send state in PassphraseAck (not needed for compatibility) Feb 13, 2020
python all: do not send state in PassphraseAck (not needed for compatibility) Feb 13, 2020
storage ci: add junit for a nice tests overview Jan 3, 2020
tests tests: better way to shut down test suite when connection to device i… Feb 13, 2020
tools ci: upload ui tests fixtures Jan 3, 2020
vendor vendor: update nanopb to 0.4.1 Feb 4, 2020
.clang-format style: fix weirdness in modtrezorio-fatfs.h Sep 12, 2019
.gitignore ci: improve pipenv caching May 24, 2019
.gitlab-ci.yml ci: ensure system Python 3.7 is used even if other pythons are available Feb 11, 2020
.gitmodules vendor: change fido2-tests to our fork Nov 1, 2019
.travis.yml ci/travis: update python to 3.7 Dec 8, 2019
CONTRIBUTING.md docs: move docs to root Dec 6, 2019
Makefile build: make sure resources are built for 'make mypy' Jan 28, 2020
Pipfile pipfile: add nanopb to Pipfile Feb 4, 2020
Pipfile.lock pipfile: add nanopb to Pipfile Feb 4, 2020
README.md docs: move docs to root Dec 6, 2019
SECURITY.md
build-docker.sh build: in build-docker.sh, remove containers after we are done Dec 11, 2019
create_monorepo.py all: replace /bin/bash with /usr/bin/env bash Sep 12, 2019
setup.cfg core: add short summary to pytest to see what failed right away Jan 28, 2020
shell.nix shell.nix: do not enforce purity Jan 16, 2020

README.md

Trezor Firmware

img

Repository Structure

  • ci: Gitlab CI configuration files
  • common/defs: JSON coin definitions and support tables
  • common/protob: Common protobuf definitions for the Trezor protocol
  • common/tools: Tools for managing coin definitions and related data
  • core: Trezor Core, firmware implementation for Trezor T
  • crypto: Stand-alone cryptography library used by both Trezor Core and the Trezor One firmware
  • docs: Assorted documentation
  • legacy: Trezor One firmware implementation
  • python: Python client library and the trezorctl command
  • storage: NORCOW storage implementation used by both Trezor Core and the Trezor One firmware
  • tests: Firmware unit test suite
  • tools: Miscellaneous build and helper scripts
  • vendor: Submodules for external dependencies

Contribute

See CONTRIBUTING.md.

Also please have a look at the docs, either in the docs folder or at docs.trezor.io before contributing. The misc chapter should be read in particular because it contains some useful assorted knowledge.

Security vulnerability disclosure

Please report suspected security vulnerabilities in private to security@satoshilabs.com, also see the disclosure section on the Trezor.io website. Please do NOT create publicly viewable issues for suspected security vulnerabilities.

Issue Labels

Priority

Label Meaning (SLA)
P1 Urgent The current release + potentially immediate hotfix (30 days)
P2 High The next release (60 days)
P3 Medium Within the next 3 releases (90 days)
P4 Low Anything outside the next 3 releases (120 days)

Severity

Label Impact
S1 Blocker Outage, broken feature with no workaround
S2 Critical Broken feature, workaround too complex & unacceptable
S3 Major Broken feature, workaround acceptable
S4 Low Functionality inconvenience or cosmetic issue

CI

The complete test suite is running on a public GitLab CI. If you are an external contributor, we also have a Travis instance where a small subset of tests is running as well - mostly style and easy fast checks, which are quite common to fail for new contributors.

Documentation

See the docs folder or visit docs.trezor.io.

You can’t perform that action at this time.