1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-12 10:58:59 +00:00
Go to file
2019-05-23 20:15:30 +02:00
ci ci: use git fetch; remove submodule strategy from specific places 2019-05-23 13:59:30 +02:00
common common/defs: remove FLASH support 2019-05-23 20:09:22 +02:00
core core: add equality function to mako template too 2019-05-22 22:46:22 +02:00
crypto Revert "crypto: add support for schnorr signatures" 2019-05-23 20:15:30 +02:00
legacy legacy: wipe with debug link only in emulator 2019-05-17 17:00:45 +02:00
python python: rename net_usage_words to max_net_usage_words 2019-05-22 16:34:22 +02:00
storage style: improve makefile output, format test files 2019-05-13 18:00:43 +02:00
tools build: centralize pb2py usage 2019-05-17 15:12:32 +02:00
vendor move vendored submodules to root vendor/ dir 2019-05-13 13:51:53 +02:00
.clang-format
.gitignore common/defs: fix invalid value in horizen.json 2019-05-14 17:08:14 +02:00
.gitlab-ci.yml ci: use git fetch; remove submodule strategy from specific places 2019-05-23 13:59:30 +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 build: fix and auto-generate mock files 2019-05-17 15:45:47 +02:00
shell.nix core: fix docker build 2019-04-30 18:03:24 +02:00

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.