arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-12 10:58:59 +00:00
Code Issues Releases Wiki Activity
8,436 Commits 317 Branches 205 Tags 188 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
a9454b216d
Go to file
Pavol Rusnak a9454b216d
core: move delay.c from trezorhal to firmware, fix prodtest build
2019-12-15 08:59:47 +00:00
.github/ISSUE_TEMPLATE github: update issue templates 2019-12-03 04:01:02 +01:00
ci ci/tests: add core emulator logs as artifacts 2019-12-09 12:17:12 +00:00
common common: apply overrides for Auxilium 2019-12-13 15:44:22 +01:00
core core: move delay.c from trezorhal to firmware, fix prodtest build 2019-12-15 08:59:47 +00:00
crypto
docs docs: fix typo 2019-12-15 08:49:15 +00:00
legacy Merge pull request #742 from trezor/language 2019-12-12 18:07:54 +01:00
python Merge pull request #742 from trezor/language 2019-12-12 18:07:54 +01:00
storage storage: move unlocked statement straight after key generation 2019-12-09 08:11:19 +00:00
tests Merge pull request #742 from trezor/language 2019-12-12 18:07:54 +01:00
tools tools/issues: style 2019-11-14 15:57:47 +00:00
vendor common: change language field to IETF BCP 47 language tag 2019-12-08 11:27:10 +01:00
.clang-format
.gitignore
.gitlab-ci.yml
.gitmodules vendor: change fido2-tests to our fork 2019-11-01 12:35:12 +01:00
.travis.yml ci/travis: update python to 3.7 2019-12-08 09:28:35 +00:00
build-docker.sh build: in build-docker.sh, remove containers after we are done 2019-12-11 14:21:07 +01:00
CONTRIBUTING.md docs: move docs to root 2019-12-06 12:24:20 +00:00
create_monorepo.py
Makefile core: auto-generate FIDO icons 2019-12-09 16:31:46 +01:00
Pipfile pip: cleanup Pipfile, run pipenv lock, update vendor/fido2-tests 2019-10-28 16:37:55 +00:00
Pipfile.lock pipenv: update packages, add missing dependencies 2019-11-20 16:13:22 +01:00
README.md docs: move docs to root 2019-12-06 12:24:20 +00:00
SECURITY.md
setup.cfg style: explicitly list shamir-mnemonic in the proper group 2019-12-09 16:31:46 +01:00
shell.nix pip: cleanup Pipfile, run pipenv lock, update vendor/fido2-tests 2019-10-28 16:37:55 +00:00

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.