arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-31 20:39:48 +00:00
Code Issues Releases Wiki Activity
7,376 Commits 332 Branches 205 Tags 231 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
ffcb5e99cc
Go to file
matejcik ffcb5e99cc mocks: fix shamir package
2019-05-17 15:12:41 +02:00
ci core+legacy: drop NOUI and HEADLESS, SDL_VIDEODRIVER works fine 2019-05-16 17:06:14 +02:00
common build: centralize pb2py usage 2019-05-17 15:12:32 +02:00
core mocks: fix shamir package 2019-05-17 15:12:41 +02:00
crypto style: improve makefile output, format test files 2019-05-13 18:00:43 +02:00
legacy legacy/firmware: fix ethereum message signing (#153) 2019-05-16 18:07:43 +02:00
python python: return generated files to git 2019-05-17 15:09:58 +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 core+legacy: rework code styling checks 2019-04-18 17:40:55 +02:00
.gitignore common/defs: fix invalid value in horizen.json 2019-05-14 17:08:14 +02:00
.gitlab-ci.yml ci: split gitlab configuration files and store them in a 'ci' folder 2019-04-28 09:31:41 +02:00
.gitmodules python: add more unit tests for ethereum message sign/verify 2019-05-16 18:10:47 +02:00
.travis.yml ci: do not install clang-format in travis, travis has its own 2019-05-14 12:59:32 +02:00
create_monorepo.py
Makefile build: new make targets for generated files 2019-05-17 15:12:41 +02:00
Pipfile build: drop python monero requirements 2019-05-14 11:24:31 +02:00
Pipfile.lock build: drop python monero requirements 2019-05-14 11:24:31 +02:00
README-monorepo.md fix link in readme 2019-04-29 19:11:44 +02:00
README.md fix typo 2019-05-14 15:48:39 +02:00
setup.cfg style: improve Makefile, stricter style rules 2019-05-07 16:31:04 +02:00
shell.nix core: fix docker build 2019-04-30 18:03:24 +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