arno
/
trezor-firmware
mirror of https://github.com/trezor/trezor-firmware.git
1
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7500 Commits
332 Branches
191 Tags
217 MiB
 
 
 
 
 
 
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '54d348228f'
${ noResults }
Go to file
Pavol Rusnak 54d348228f
all: rename TREZOR to Trezor where possible 		5 years ago
ci ci/legacy: don't build bootloader/demo in bitcoinonly+debug targets 5 years ago
common all: rename TREZOR to Trezor where possible 5 years ago
core all: rename TREZOR to Trezor where possible 5 years ago
crypto all: rename TREZOR to Trezor where possible 5 years ago
legacy all: rename TREZOR to Trezor where possible 5 years ago
python all: rename TREZOR to Trezor where possible 5 years ago
storage all: rename TREZOR to Trezor where possible 5 years ago
tools build: centralize pb2py usage 5 years ago
vendor core/secp256k1-zkp: use ARM assembly for field operations (#176) 5 years ago
.clang-format core+legacy: rework code styling checks 5 years ago
.gitignore ci: improve pipenv caching 5 years ago
.gitlab-ci.yml ci: improve pipenv caching 5 years ago
.gitmodules submodules: remove secp256k1-zkp's branch name because it will rotate 5 years ago
.travis.yml ci: run codegen checks 5 years ago
Makefile build: add build and check target for coins.json 5 years ago
Pipfile build: require new enough flake8 for per-file-ignores 5 years ago
Pipfile.lock build: require new enough flake8 for per-file-ignores 5 years ago
README-monorepo.md fix link in readme 5 years ago
README.md README: add note on CI 5 years ago
SECURITY.md add SECURITY.md 5 years ago
create_monorepo.py monorepo: add notes and creation tool 5 years ago
setup.cfg python: more consistent handling of markers in device_tests 5 years ago
shell.nix core: fix docker build 5 years ago

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.