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,990 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%
315a30b42b
Go to file
Andrew Kozlik 315a30b42b core/webauthn: Disable FIDO2 signature counter for some relying parties
2019-09-19 16:16:58 +02:00
ci ci: build u2f test suite 2019-09-14 14:59:11 +02:00
common core/webauthn: Disable FIDO2 signature counter for some relying parties 2019-09-19 16:16:58 +02:00
core core/webauthn: Disable FIDO2 signature counter for some relying parties 2019-09-19 16:16:58 +02:00
crypto git subrepo pull crypto 2019-09-12 11:52:12 +02:00
docs/git/hooks
legacy legacy: Add SdProtect to SKIPPED_MESSAGES 2019-09-18 18:55:58 +02:00
python core/webauthn: Disable FIDO2 signature counter for some relying parties 2019-09-19 16:16:58 +02:00
storage storage: Add external salt parameter to unlock() and change_pin(). 2019-09-18 18:53:42 +02:00
tests python/tests: Add SD protection device test. 2019-09-18 18:55:58 +02:00
tools common/messages: Add credential management message. 2019-09-17 18:32:31 +02:00
vendor
.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
.travis.yml
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
shell.nix nix: add flaky to python packages 2019-09-10 11:30:05 +02:00

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.