您最多能選擇 25 個主題 主題必須以字母或數字為開頭,可包含連接號「-」且最長為 35 個字元。
 
 
 
 
 
 
移至檔案
tychovrahe f2de9c5b86
fixup! fix(core/rust): fix bindgen macros generation
5 小時前
.clusterfuzzlite Run fuzzer in CI 10 個月前
.github feat(core): copy T2T1 bootloader UI for T3T1 2 週前
ci chore(ci): make arm emulator versions build only in main branches 2 週前
common fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. 2 週前
core fixup! fix(core/rust): fix bindgen macros generation 5 小時前
crypto fix(crypto): imporve handling of return value 6 天前
docs docs: minor fix of build emu 1 週前
legacy fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. 2 週前
python chore(core): add T3T1 production keys to trezorctl 1 週前
rust feat(rust/trezor_client): add solana_get_address example 2 個月前
storage feat(core): use U5 HW keys to additionally encrypt storage items 2 週前
tests fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. 2 週前
tools feat(crypto): Add Brian Gladman's implementation of GCM. 3 週前
vendor chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. 2 個月前
.clang-format clang-format: set the IncludeBlocks setting to "Preserve" 4 年前
.editorconfig style: add .editorconfig [skip ci] 4 年前
.gitattributes chore: tag generated files for github diffs 1 個月前
.gitignore fix(core,crypto): add more test cases from bip-173 3 年前
.gitlab-ci.yml ci: move hardware tests over to github actions 2 個月前
.gitmodules chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. 2 個月前
.pylintrc chore: move pylint config from setup.cfg to .pylintrc 5 個月前
.yamllint.yml style: ignore yaml files in venv 3 年前
CODEOWNERS chore(CODEOWNERS): remove me from some components 3 年前
COMMITS.md docs: introduce conventional-commits (#1234) 4 年前
CONTRIBUTING.md docs: add PR workflow info; move CONTRIBUTING to docs 4 年前
COPYING docs: clear up licensing information 3 年前
LICENSE.md docs: clear up licensing information 3 年前
Makefile feat(crypto): Add Brian Gladman's implementation of GCM. 3 週前
README.md chore(readme): add link to trezor.io KB disclosure article 1 年前
SECURITY.md docs: use monospace for fingerprints 5 年前
build-docker.sh build: allow targets list in build-docker.sh 1 週前
create_monorepo.py chore: update branch name to main where its used 6 個月前
poetry.lock build(deps): drop curve25519-donna and ed25519 from deps 1 週前
poetry.toml build(poetry): use new (parallel) installer 1 年前
pyproject.toml build(deps): drop curve25519-donna and ed25519 from deps 1 週前
setup.cfg chore: upgrade style checkers 2 個月前
shell.nix nix: unify ci/shell.nix and shell.nix 4 年前

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

See CONTRIBUTING.md.

Using Conventional Commits is strongly recommended and might be enforced in future.

Also please have a look at the docs, either in the docs folder or at docs.trezor.io before contributing. The misc chapter should be read in particular because it contains some useful assorted knowledge.

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.

Documentation

See the docs folder or visit docs.trezor.io.