arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2025-04-11 04:45:45 +00:00
Code Issues Releases Wiki Activity
7,686 Commits 476 Branches 212 Tags 209 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
0e224644b6
Go to file
Pavol Rusnak 0e224644b6
legacy: don't add more pixels than needed in oledSCA 
(cherry picked from commit 6720690452)
2019-08-07 12:43:51 +02:00
ci ci: change docker image's url to new gitlab 2019-08-02 17:08:13 +02:00
common
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
legacy legacy: don't add more pixels than needed in oledSCA 2019-08-07 12:43:51 +02:00
python tests: drop usages of read_passphrase_protection 2019-08-02 19:06:26 +02:00
storage
tools protobuf: add enum value validation (#363) 2019-08-02 19:06:01 +02:00
vendor core/secp256k1-zkp: use ARM assembly for field operations (#176) 2019-05-25 11:42:13 +02:00
.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 ci: run codegen checks 2019-05-17 15:49:01 +02:00
create_monorepo.py
Makefile
Pipfile
Pipfile.lock Pipenv: reinstall Pipfile.lock 2019-07-24 12:16:26 +02:00
README-monorepo.md fix link in readme 2019-04-29 19:11:44 +02:00
README.md README: add note on CI 2019-05-23 13:19:44 +02:00
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.