arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-19 14:30:31 +00:00
Code Issues Releases Wiki Activity
8,880 Commits 322 Branches 205 Tags 196 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
80a07ca4af
Go to file
Pavol Rusnak 80a07ca4af
vendor: update fido2-tests
2020-04-08 14:11:01 +02:00
.github/ISSUE_TEMPLATE
ci ci: set artifacts' name using the job name and commit hash 2020-04-07 10:42:45 +02:00
common common: Fix maintainer email for vipstar/bitzeny (#891) 2020-04-02 11:13:59 +02:00
core core: drop sys.pyi from mocks (fixes #934) 2020-04-08 11:19:26 +02:00
crypto crypto: fix last commit 2020-02-17 19:16:54 +00:00
docs docs: document when firmware wipes storage 2020-03-25 19:06:57 +01:00
legacy legacy, tests: Check for invalid PIN. 2020-03-17 11:53:48 +01:00
python Adding @jonathancross to AUTHORS 2020-04-06 10:11:08 +02:00
storage storage: Add storage_ensure_not_wipe_code(). 2020-03-19 15:04:33 +01:00
tests tests/u2f-hid: Disable strict timing checks in HIDTest and increase receive timeout to avoid failures in CI when emulator is slow to respond. 2020-04-06 09:53:42 +02:00
tools
vendor vendor: update fido2-tests 2020-04-08 14:11:01 +02:00
.clang-format
.gitignore add .DS_Store to .gitignore (#900) 2020-03-11 20:22:56 +01:00
.gitlab-ci.yml ci: add a generic timeout to GitLab pytest runs 2020-03-09 10:31:40 +01:00
.gitmodules
.travis.yml ci: check if commit message contains fixup on travis 2020-03-06 18:45:46 +00:00
build-docker.sh
CONTRIBUTING.md
create_monorepo.py
Makefile python: drop coins.json (fixes #752) 2020-03-26 11:30:06 +01:00
Pipfile pipenv: change fido2 version to >= 0.8.0, run pipenv update 2020-04-08 09:22:40 +00:00
Pipfile.lock pipenv: change fido2 version to >= 0.8.0, run pipenv update 2020-04-08 09:22:40 +00:00
README.md
SECURITY.md docs: use monospace for fingerprints 2019-08-16 18:47:46 +02:00
setup.cfg tests: silence pytest 6.0 warning 2020-03-26 11:30:06 +01:00
shell.nix

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.