arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-12 19:09:10 +00:00
Code Issues Releases Wiki Activity
7,607 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%
1480f754f4
Go to file
Tomas Susanka 1480f754f4 build
2019-07-22 15:32:41 +02:00
ci ci/legacy: don't build bootloader/demo in bitcoinonly+debug targets 2019-06-11 17:01:13 +02:00
common common/protobuf: replace ResetDevice.slip39 with enum 2019-07-22 15:22:44 +02:00
core build 2019-07-22 15:32:41 +02:00
crypto core: add slip39 keyboard 2019-06-23 21:33:58 +02:00
docs/git/hooks docs: set hook as executable 2019-07-12 12:55:48 +02:00
legacy webauthn: Add Binance to knownapps. Add Binance icon. 2019-07-12 11:38:44 +02:00
python build 2019-07-22 15:32:41 +02:00
storage storage: fix incomatibility with new pytest 2019-07-09 14:47:24 +02:00
tools core/messages: don't generate unused messages 2019-07-01 15:52:36 +02:00
vendor core/secp256k1-zkp: use ARM assembly for field operations (#176) 2019-05-25 11:42:13 +02:00
.clang-format core+legacy: rework code styling checks 2019-04-18 17:40:55 +02:00
.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 submodules: remove secp256k1-zkp's branch name because it will rotate 2019-06-04 08:21:42 +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 core/typing: add mypy 2019-07-09 12:51:48 +02:00
Pipfile.lock re-enable shamir mnemonic tests 2019-07-22 13:25:08 +02:00
README-monorepo.md fix link in readme 2019-04-29 19:11:44 +02:00
README.md README: add note on CI 2019-05-23 13:19:44 +02:00
SECURITY.md add SECURITY.md 2019-06-06 19:50:57 +02:00
setup.cfg core/typing: add annotations 2019-07-09 12:51:48 +02:00
shell.nix nix: add coverage python package 2019-06-26 22:25:04 +02:00

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.