arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-25 17:09:44 +00:00
Code Issues Releases Wiki Activity
7,995 Commits 352 Branches 205 Tags 213 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
d96c2e0dae
Go to file
hatchpay d96c2e0dae common/defs: add HATCH (#543)
2019-09-19 18:00:48 +02:00
ci
common common/defs: add HATCH (#543) 2019-09-19 18:00:48 +02:00
core core/storage: Rename APP_FIDO2 to APP_WEBAUTHN. 2019-09-19 17:17:22 +02:00
crypto
docs/git/hooks
legacy legacy: Add SdProtect to SKIPPED_MESSAGES 2019-09-18 18:55:58 +02:00
python Merge pull request #538 from trezor/andrewkozlik/fido2-signcount 2019-09-19 17:00:51 +02:00
storage storage: Add external salt parameter to unlock() and change_pin(). 2019-09-18 18:53:42 +02:00
tests core: refactor slip39 2019-09-19 16:38:29 +02:00
tools common/messages: Add credential management message. 2019-09-17 18:32:31 +02:00
vendor
.clang-format
.gitignore
.gitlab-ci.yml
.gitmodules
.travis.yml
build-docker.sh
create_monorepo.py
Makefile build: add help to make style/style_check 2019-08-29 12:46:06 +02:00
Pipfile
Pipfile.lock
README-monorepo.md
README.md
SECURITY.md
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.