1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-10-12 19:09:10 +00:00
Go to file
2019-09-20 18:06:02 +02:00
ci ci: build u2f test suite 2019-09-14 14:59:11 +02:00
common git subrepo push common 2019-09-19 18:08:22 +02:00
core core: clean up backup type handling in reset_device 2019-09-20 18:00:14 +02:00
crypto git subrepo pull crypto 2019-09-12 11:52:12 +02:00
docs/git/hooks git/hooks: do not suppress output 2019-08-02 10:39:55 +02:00
legacy legacy: Add SdProtect to SKIPPED_MESSAGES 2019-09-18 18:55:58 +02:00
python tests: only allow input_flow in a with-block 2019-09-20 15:47:34 +02:00
storage storage: Add external salt parameter to unlock() and change_pin(). 2019-09-18 18:53:42 +02:00
tests tests: add check that backup succeeded 2019-09-20 18:06:02 +02:00
tools common/messages: Add credential management message. 2019-09-17 18:32:31 +02:00
vendor core/secp256k1-zkp: use ARM assembly for field operations (#176) 2019-05-25 11:42:13 +02:00
.clang-format style: fix weirdness in modtrezorio-fatfs.h 2019-09-12 16:49:51 +02:00
.gitignore
.gitlab-ci.yml ci: deploy frozen emulators to upgrade tests 2019-09-10 14:42:14 +02:00
.gitmodules submodules: remove secp256k1-zkp's branch name because it will rotate 2019-06-04 08:21:42 +02:00
.travis.yml ci: use pipenv sync 2019-08-12 12:57:25 +02:00
build-docker.sh all: replace /bin/bash with /usr/bin/env bash 2019-09-12 17:35:55 +02:00
create_monorepo.py all: replace /bin/bash with /usr/bin/env bash 2019-09-12 17:35:55 +02:00
Makefile build: add help to make style/style_check 2019-08-29 12:46:06 +02:00
Pipfile python: clarify requirements, enable tox in CI 2019-08-12 12:57:25 +02:00
Pipfile.lock python: clarify requirements, enable tox in CI 2019-08-12 12:57:25 +02:00
README-monorepo.md
README.md
SECURITY.md docs: use monospace for fingerprints 2019-08-16 18:47:46 +02:00
setup.cfg tests: run default set of tests from root 2019-08-12 12:57:25 +02:00
shell.nix nix: add flaky to python packages 2019-09-10 11:30:05 +02:00

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.