arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-26 01:18:28 +00:00
Code Issues Releases Wiki Activity
7,421 Commits 351 Branches 205 Tags 213 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
8a179437b1
Go to file
Roman Zeyde 8a179437b1
core: add custom markers to pytest.ini 
Following https://docs.pytest.org/en/latest/mark.html#registering-marks
2019-05-25 12:09:45 +02:00
ci core: regenerate templates 2019-05-23 20:24:44 +02:00
common common+python: Revert Ontology support 2019-05-25 11:59:35 +02:00
core core: add custom markers to pytest.ini 2019-05-25 12:09:45 +02:00
crypto Revert "crypto: add support for schnorr signatures" 2019-05-23 20:15:30 +02:00
legacy legacy: wipe with debug link only in emulator 2019-05-17 17:00:45 +02:00
python common+python: Revert Ontology support 2019-05-25 11:59:35 +02:00
storage
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
create_monorepo.py
Makefile
Pipfile
Pipfile.lock
README-monorepo.md
README.md README: add note on CI 2019-05-23 13:19:44 +02:00
setup.cfg tests: remove xfail 2019-05-25 11:59: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.