arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-14 03:30:02 +00:00
Code Issues Releases Wiki Activity
8,343 Commits 336 Branches 206 Tags 189 MiB
Python 34.6%
C 33.7%
Rust 29.4%
Nix 0.6%
C++ 0.4%
Other 1.1%
8e4de5e929
Go to file
matejcik 8e4de5e929 python/trezorctl: split trezorctl into separate modules 
Instead of all commands (like `load-device`, `change-pin`,
`tezos-sign-tx`, `ethereum-verify-message`...) living in trezorctl.py,
each functional group is now defined in a separate file.

With that, better structuring of the trezorctl command becomes
available:
- instead of `trezorctl set-label`, use `trezorctl set label`
- instead of `trezorctl change-pin`, use `trezorctl set pin`
- instead of `trezorctl enable-passphrase`, use `trezorctl set
passphrase enabled`

For common commands, such as `sign-tx`, it is possible to use the
currency name or shortcut:

- `trezorctl btc sign-tx`
- `trezorctl ethereum sign-tx`
- `trezorctl xtz sign-tx`
- `trezorctl doge sign-tx`
etc.

Some aliases have been retained for better compatibility. For others,
refer to `trezorctl --help` and `trezorctl <command> --help`.
2019-11-18 11:50:07 +01:00
ci ci/tests: use new Monero tests binary 2019-11-13 16:29:06 +01:00
common all: drop XPRV feature of LoadDevice 2019-11-13 16:48:35 +01:00
core core/webauthn: update metadata 2019-11-16 10:53:10 +00:00
crypto all: let's use -Wno-missing-braces because clang does not respect 2019-10-11 09:59:32 +02:00
docs docs: improve docs, add random.md 2019-10-24 13:36:54 +02:00
legacy core+legacy: remove confusing changelog entries 2019-11-13 19:47:35 +01:00
python python/trezorctl: split trezorctl into separate modules 2019-11-18 11:50:07 +01:00
storage storage: introduce FLAGS_APPID 2019-11-11 19:47:48 +01:00
tests tests: improve clicktests 2019-11-15 15:54:16 +01:00
tools tools/issues: style 2019-11-14 15:57:47 +00:00
vendor core/tests: adapt device_emu_fido2/u2f to reordered usb endpoints 2019-11-13 13:21:39 +01:00
.clang-format style: fix weirdness in modtrezorio-fatfs.h 2019-09-12 16:49:51 +02:00
.gitignore ci: improve pipenv caching 2019-05-24 09:18:00 +02:00
.gitlab-ci.yml gitlab-ci: checking if pipenv exists 2019-10-16 10:27:27 +02:00
.gitmodules vendor: change fido2-tests to our fork 2019-11-01 12:35:12 +01:00
.travis.yml build: update protobuf dependency to 3.6.1 2019-10-02 13:07:48 +00: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 pip: cleanup Pipfile, run pipenv lock, update vendor/fido2-tests 2019-10-28 16:37:55 +00:00
Pipfile.lock pip: cleanup Pipfile, run pipenv lock, update vendor/fido2-tests 2019-10-28 16:37:55 +00:00
README-monorepo.md fix link in readme 2019-04-29 19:11:44 +02:00
README.md readme: add link to GitLab CI 2019-10-25 13:32:56 +00:00
SECURITY.md docs: use monospace for fingerprints 2019-08-16 18:47:46 +02:00
setup.cfg mypy: add show_error_codes to setup.cfg 2019-10-02 11:12:34 +02:00
shell.nix pip: cleanup Pipfile, run pipenv lock, update vendor/fido2-tests 2019-10-28 16:37:55 +00:00

README.md

Trezor Firmware

img

Repository Structure

  • ci: Gitlab CI configuration files
  • common/defs: JSON coin definitions and support tables
  • common/protob: Common protobuf definitions for the Trezor protocol
  • common/tools: Tools for managing coin definitions and related data
  • core: Trezor Core, firmware implementation for Trezor T
  • crypto: Stand-alone cryptography library used by both Trezor Core and the Trezor One firmware
  • docs: Assorted documentation
  • legacy: Trezor One firmware implementation
  • python: Python client library and the trezorctl command
  • storage: NORCOW storage implementation used by both Trezor Core and the Trezor One firmware
  • tests: Firmware unit test suite
  • tools: Miscellaneous build and helper scripts
  • vendor: Submodules for external dependencies

Contribute

Inspired by GitLab Contributing Guide

Make sure to check out general contribution guidelines on the Trezor Wiki. If you are contributing to Trezor Core (the Trezor T firmware), make sure to check out Trezor Core contribution guidelines as well.

Some useful assorted knowledge can be found in the docs subdirectory.

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 a public 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.