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,365 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%
9ce8d0a9da
Go to file
Andrew Kozlik 9ce8d0a9da
Merge pull request #734 from trezor/andrewkozlik/733 
Fix continuous display blinking with Android
2019-12-04 13:11:03 +01:00
.github/ISSUE_TEMPLATE github: update issue templates 2019-12-03 04:01:02 +01:00
ci ci/docker: use gcc-arm-embedded 9 2019-12-01 19:30:10 +01:00
common Update wallets.json (#725) 2019-11-25 04:58:51 +01:00
core core/webauthn: Allow only one CTAPHID_WINK command at a time on any given channel ID to fix continuous display blinking with Android. 2019-12-03 14:18:43 +01:00
crypto
docs
legacy all: disallow most RecoveryDevice fields in dry-run (fixes #666) 2019-11-20 12:27:57 +01:00
python all: disallow most RecoveryDevice fields in dry-run (fixes #666) 2019-11-20 12:27:57 +01:00
storage storage: introduce FLAGS_APPID 2019-11-11 19:47:48 +01:00
tests all: disallow most RecoveryDevice fields in dry-run (fixes #666) 2019-11-20 12:27:57 +01:00
tools tools/issues: style 2019-11-14 15:57:47 +00:00
vendor vendor: Update fido2-tests submodule to fix issues with random ordering. 2019-11-26 15:18:14 +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
build-docker.sh ci/docker: use gcc-arm-embedded 9 2019-12-01 19:30:10 +01:00
create_monorepo.py all: replace /bin/bash with /usr/bin/env bash 2019-09-12 17:35:55 +02:00
Makefile
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-monorepo.md
README.md
SECURITY.md
setup.cfg
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

Inspired by GitLab Contributing Guide

Make sure to check out general contribution guidelines on the Trezor Wiki. If you are contributing to Trezor Core (the Trezor T firmware), make sure to check out Trezor Core contribution guidelines as well.

Some useful assorted knowledge can be found in the docs subdirectory.

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.