arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-13 03:19:05 +00:00
Code Issues Releases Wiki Activity
7,425 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%
23202e2479
Go to file
Pavol Rusnak 23202e2479
core: remove pytest.ini because it hides setup.cfg from root
2019-05-25 13:37:34 +02:00
ci core: regenerate templates 2019-05-23 20:24:44 +02:00
common common: more TRX cleanup 2019-05-25 12:48:04 +02:00
core core: remove pytest.ini because it hides setup.cfg from root 2019-05-25 13:37:34 +02:00
crypto Revert "crypto: add support for schnorr signatures" 2019-05-23 20:15:30 +02:00
legacy common: more TRX cleanup 2019-05-25 12:48:04 +02:00
python common: more TRX cleanup 2019-05-25 12:48:04 +02:00
storage
tools build: centralize pb2py usage 2019-05-17 15:12:32 +02:00
vendor core/secp256k1-zkp: use ARM assembly for field operations (#176) 2019-05-25 11:42:13 +02:00
.clang-format
.gitignore ci: improve pipenv caching 2019-05-24 09:18:00 +02:00
.gitlab-ci.yml ci: improve pipenv caching 2019-05-24 09:18:00 +02:00
.gitmodules python: add more unit tests for ethereum message sign/verify 2019-05-16 18:10:47 +02:00
.travis.yml ci: run codegen checks 2019-05-17 15:49:01 +02:00
create_monorepo.py
Makefile build: add build and check target for coins.json 2019-05-17 15:48:17 +02:00
Pipfile build: require new enough flake8 for per-file-ignores 2019-05-17 15:45:51 +02:00
Pipfile.lock build: require new enough flake8 for per-file-ignores 2019-05-17 15:45:51 +02:00
README-monorepo.md
README.md README: add note on CI 2019-05-23 13:19:44 +02:00
setup.cfg root: move pytest markers to setup.cfg 2019-05-25 13:06:28 +02:00
shell.nix

README.md

Trezor Firmware

img

Contribute

Inspired by GitLab Contributing Guide

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 our internal 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.