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,516 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%
435d00114c
Go to file
Tomas Susanka 435d00114c
SLIP-39 MVP (#195) 
SLIP-39 MVP
2019-06-23 21:48:09 +02:00
ci ci/legacy: don't build bootloader/demo in bitcoinonly+debug targets 2019-06-11 17:01:13 +02:00
common common: add slip39 flag to reset_device 2019-06-23 21:27:06 +02:00
core core: add slip39 support to reset and recovery device 2019-06-23 21:33:58 +02:00
crypto core: add slip39 keyboard 2019-06-23 21:33:58 +02:00
legacy all: rename TREZOR to Trezor where possible 2019-06-17 20:28:29 +02:00
python python: add device test for SLIP-39 recovery device; fix reset device 2019-06-23 21:33:58 +02:00
storage all: rename TREZOR to Trezor where possible 2019-06-17 20:28:29 +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 submodules: remove secp256k1-zkp's branch name because it will rotate 2019-06-04 08:21:42 +02:00
.travis.yml
create_monorepo.py
Makefile
Pipfile
Pipfile.lock
README-monorepo.md
README.md
SECURITY.md add SECURITY.md 2019-06-06 19:50:57 +02:00
setup.cfg python: more consistent handling of markers in device_tests 2019-05-27 16:38:35 +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.