1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-20 06:49:14 +00:00
Go to file
2020-05-12 09:48:23 +00:00
.github/ISSUE_TEMPLATE
ci ci/fido2: check if another emu is not running 2020-05-06 14:36:11 +00:00
common git subrepo push common 2020-05-12 09:19:18 +02:00
core tests: use maxfail option for fido2 tests 2020-05-12 09:48:23 +00:00
crypto
docs docs: add coinmate and liskish wallet to third parties 2020-05-05 11:37:19 +00:00
legacy core, legacy: bump versions 2020-04-24 17:12:20 +00:00
python python: style 2020-05-05 07:05:53 +00:00
storage storage: Add storage_ensure_not_wipe_code(). 2020-03-19 15:04:33 +01:00
tests core: disable passphrase_always_on_device when turning off passphrase 2020-04-28 14:54:18 +02:00
tools ci: upload ui tests fixtures 2020-01-03 15:07:46 +00:00
vendor
.clang-format clang-format: set the IncludeBlocks setting to "Preserve" 2020-05-04 17:17:06 +02:00
.gitignore
.gitlab-ci.yml
.gitmodules
.travis.yml
build-docker.sh
CODEOWNERS CODEOWNERS: add more people 2020-05-09 22:24:35 +02:00
CONTRIBUTING.md docs: add PR workflow info; move CONTRIBUTING to docs 2020-04-30 14:49:47 +02:00
create_monorepo.py
Makefile
Pipfile pipenv: add serial 2020-04-10 11:23:07 +02:00
Pipfile.lock
README.md readme: fix link to Contributing 2020-04-30 15:03:56 +02:00
SECURITY.md
setup.cfg
shell.nix nix: add git to shell.nix 2020-05-04 18:45: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.

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.