arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-14 03:30:02 +00:00
Code Issues Releases Wiki Activity
7,493 Commits 336 Branches 206 Tags 189 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
ebc22e5ccb
Go to file
Pavol Rusnak ebc22e5ccb
ci/legacy: don't build bootloader/demo in bitcoinonly+debug targets
2019-06-11 17:01:13 +02:00
ci ci/legacy: don't build bootloader/demo in bitcoinonly+debug targets 2019-06-11 17:01:13 +02:00
common common/defs: add Bitcore backends to CRW (#234) 2019-06-08 23:01:39 +02:00
core Merge pull request #239 from trezor/andrewkozlik/hmac_drbg 2019-06-11 16:59:50 +02:00
crypto crypto/hmac_drbg: Fix buffer overflow. 2019-06-11 11:41:40 +02:00
legacy legacy/common: Temporarily use TRNG to generate random delays. 2019-06-11 11:41:40 +02:00
python
storage storage: Use wait_random() from common.h. Fix build for tests. 2019-06-11 11:41:40 +02:00
tools
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
.travis.yml ci: run codegen checks 2019-05-17 15:49:01 +02:00
create_monorepo.py monorepo: add notes and creation tool 2019-04-15 19:16:04 +02:00
Makefile
Pipfile
Pipfile.lock
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
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.