1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-12-18 04:18:10 +00:00
Go to file
2023-08-29 10:59:34 +02:00
.clusterfuzzlite Run fuzzer in CI 2023-07-12 10:13:17 +02:00
.github Run fuzzer in CI 2023-07-12 10:13:17 +02:00
ci feat(ci): add firmware.elf size checkers into CI 2023-07-27 13:34:29 +02:00
common feat(common): add model and color information (fixes #3160) 2023-08-28 16:50:20 +02:00
core feat(core): Implement comparison of OPTIGA metadata. 2023-08-29 10:59:34 +02:00
crypto feat(crypto): Implement AES-CCM. 2023-08-29 10:59:34 +02:00
docs docs(core): add protoc installation instructions 2023-08-16 10:48:32 +02:00
legacy style(legacy): apply isort 5 2023-08-16 13:29:51 +02:00
python fix(core/python): print correct model in print_firmware_version 2023-08-22 11:23:29 +02:00
rust docs(rust/trezor-client): update readme 2023-08-10 10:10:51 +02:00
storage style(storage): apply isort 5 2023-08-16 13:29:51 +02:00
tests chore(tests): regenerate fixtures 2023-08-28 12:09:58 +02:00
tools feat(crypto): Implement AES-CCM. 2023-08-29 10:59:34 +02:00
vendor build: fix compilation on darwin 2023-05-10 20:59:00 +02:00
.clang-format clang-format: set the IncludeBlocks setting to "Preserve" 2020-05-04 17:17:06 +02:00
.editorconfig style: add .editorconfig [skip ci] 2020-11-05 16:45:52 +01:00
.gitignore fix(core,crypto): add more test cases from bip-173 2021-07-21 11:20:11 +02:00
.gitlab-ci.yml ci: allow jobs to be cancelled when redundant 2023-07-19 17:26:11 +02:00
.gitmodules feat(common): switch to external Ethereum definitions, add generators 2023-03-24 13:24:46 +01:00
.yamllint.yml style: ignore yaml files in venv 2021-06-08 09:55:19 +02:00
build-docker.sh build: differentiate between models for prodtest build 2023-06-14 12:23:03 +02:00
CODEOWNERS chore(CODEOWNERS): remove me from some components 2021-10-17 10:45:14 +02:00
COMMITS.md docs: introduce conventional-commits (#1234) 2020-09-15 16:11:39 +02:00
CONTRIBUTING.md docs: add PR workflow info; move CONTRIBUTING to docs 2020-04-30 14:49:47 +02:00
COPYING docs: clear up licensing information 2021-03-31 18:51:52 +02:00
create_monorepo.py all: replace /bin/bash with /usr/bin/env bash 2019-09-12 17:35:55 +02:00
LICENSE.md docs: clear up licensing information 2021-03-31 18:51:52 +02:00
Makefile feat(core): support checking generated vendor headers as part of make gen_check 2023-08-15 09:37:38 +02:00
poetry.lock chore: upgrade to isort 5 2023-08-16 13:29:51 +02:00
poetry.toml build(poetry): use new (parallel) installer 2022-11-08 12:21:46 +01:00
pyproject.toml chore: upgrade to isort 5 2023-08-16 13:29:51 +02:00
README.md chore(readme): add link to trezor.io KB disclosure article 2023-01-09 10:45:31 +01:00
SECURITY.md docs: use monospace for fingerprints 2019-08-16 18:47:46 +02:00
setup.cfg chore: upgrade to isort 5 2023-08-16 13:29:51 +02:00
shell.nix nix: unify ci/shell.nix and shell.nix 2020-07-03 12:32:55 +02:00

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.

Using Conventional Commits is strongly recommended and might be enforced in future.

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.

Documentation

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