No puede seleccionar más de 25 temas Los temas deben comenzar con una letra o número, pueden incluir guiones ('-') y pueden tener hasta 35 caracteres de largo.
 
 
 
 
 
 
Ir al archivo
obrusvit 3628630584
feat(core/ui): improve T3T1 recovery
hace 11 horas
.clusterfuzzlite Run fuzzer in CI hace 10 meses
.github feat(core): copy T2T1 bootloader UI for T3T1 hace 2 semanas
ci feat(core/ui): rust-based UI flows hace 1 semana
common fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. hace 2 semanas
core feat(core/ui): improve T3T1 recovery hace 11 horas
crypto chore(crypto): Zero-initialize stack variables in AES code. hace 3 semanas
docs docs: minor fix of build emu hace 1 semana
legacy fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. hace 2 semanas
python feat(core): add icons for T3T1 hace 1 semana
rust refactor(core): improve tjpg interface hace 1 semana
storage feat(core): use U5 HW keys to additionally encrypt storage items hace 3 semanas
tests feat(core): T3T1 ShareWords component hace 1 semana
tools feat(crypto): Add Brian Gladman's implementation of GCM. hace 3 semanas
vendor chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. hace 2 meses
.clang-format clang-format: set the IncludeBlocks setting to "Preserve" hace 4 años
.editorconfig style: add .editorconfig [skip ci] hace 4 años
.gitattributes chore: tag generated files for github diffs hace 1 mes
.gitignore fix(core,crypto): add more test cases from bip-173 hace 3 años
.gitlab-ci.yml ci: move hardware tests over to github actions hace 2 meses
.gitmodules chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. hace 2 meses
.pylintrc chore: move pylint config from setup.cfg to .pylintrc hace 5 meses
.yamllint.yml style: ignore yaml files in venv hace 3 años
CODEOWNERS chore(CODEOWNERS): remove me from some components hace 3 años
COMMITS.md docs: introduce conventional-commits (#1234) hace 4 años
CONTRIBUTING.md docs: add PR workflow info; move CONTRIBUTING to docs hace 4 años
COPYING docs: clear up licensing information hace 3 años
LICENSE.md docs: clear up licensing information hace 3 años
Makefile feat(crypto): Add Brian Gladman's implementation of GCM. hace 3 semanas
README.md chore(readme): add link to trezor.io KB disclosure article hace 1 año
SECURITY.md docs: use monospace for fingerprints hace 5 años
build-docker.sh build: differentiate between models for prodtest build hace 11 meses
create_monorepo.py chore: update branch name to main where its used hace 6 meses
poetry.lock build(deps): bump idna from 3.3 to 3.7 hace 2 semanas
poetry.toml build(poetry): use new (parallel) installer hace 1 año
pyproject.toml feat: Remove pyblake2 hace 1 mes
setup.cfg chore: upgrade style checkers hace 2 meses
shell.nix nix: unify ci/shell.nix and shell.nix hace 4 años

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.