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,689 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%
ee95e58f4a
Go to file
Pavol Rusnak ee95e58f4a
legacy: use fixed font for showing internal entropy 
(cherry picked from commit 3b1f44945a)
2019-08-07 12:43:52 +02:00
ci ci: change docker image's url to new gitlab 2019-08-02 17:08:13 +02:00
common protobuf: add enum value validation (#363) 2019-08-02 19:06:01 +02:00
core core/protobuf: fix 5b6fa113 2019-08-07 10:59:22 +02:00
crypto cardano: Implement SLIP-0023 and add SLIP-0039 support for Cardano. 2019-07-25 19:43:05 +02:00
docs/git/hooks git/hooks: do not suppress output 2019-08-02 10:39:55 +02:00
legacy legacy: use fixed font for showing internal entropy 2019-08-07 12:43:52 +02:00
python tests: drop usages of read_passphrase_protection 2019-08-02 19:06:26 +02:00
storage storage: fix incomatibility with new pytest 2019-07-09 14:47:24 +02:00
tools protobuf: add enum value validation (#363) 2019-08-02 19:06:01 +02:00
vendor
.clang-format
.gitignore
.gitlab-ci.yml ci: update docker; no need for TLS in internal env 2019-07-29 15:23:26 +02:00
.gitmodules
.travis.yml
create_monorepo.py
Makefile make: run flake8 during style check as well 2019-08-06 10:08:23 +02:00
Pipfile
Pipfile.lock Pipenv: reinstall Pipfile.lock 2019-07-24 12:16:26 +02:00
README-monorepo.md
README.md
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

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.