25'ten fazla konu seçemezsiniz Konular bir harf veya rakamla başlamalı, kısa çizgiler ('-') içerebilir ve en fazla 35 karakter uzunluğunda olabilir.
 
 
 
 
 
 
Dosyaya git
Martin Milata 87d57535cf
fix(core): macos build with signed char
11 saat önce
.clusterfuzzlite Run fuzzer in CI 10 ay önce
.github feat(core): copy T2T1 bootloader UI for T3T1 2 hafta önce
ci feat(core/ui): rust-based UI flows 6 gün önce
common fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. 2 hafta önce
core fix(core): macos build with signed char 11 saat önce
crypto chore(crypto): Zero-initialize stack variables in AES code. 3 hafta önce
docs docs: minor fix of build emu 1 hafta önce
legacy fix(legacy): resolves the issue of incorrect signature generation when the Stellar transaction source account differs from the signing account. 2 hafta önce
python feat(core): add icons for T3T1 6 gün önce
rust refactor(core): improve tjpg interface 7 gün önce
storage feat(core): use U5 HW keys to additionally encrypt storage items 2 hafta önce
tests feat(core): T3T1 ShareWords component 6 gün önce
tools feat(crypto): Add Brian Gladman's implementation of GCM. 3 hafta önce
vendor chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. 2 ay önce
.clang-format clang-format: set the IncludeBlocks setting to "Preserve" 4 yıl önce
.editorconfig style: add .editorconfig [skip ci] 4 yıl önce
.gitattributes chore: tag generated files for github diffs 1 ay önce
.gitignore fix(core,crypto): add more test cases from bip-173 3 yıl önce
.gitlab-ci.yml ci: move hardware tests over to github actions 2 ay önce
.gitmodules chore(core): change STM32Cube submodule to separate hal driver and cmsis submodules. 2 ay önce
.pylintrc chore: move pylint config from setup.cfg to .pylintrc 5 ay önce
.yamllint.yml style: ignore yaml files in venv 3 yıl önce
CODEOWNERS chore(CODEOWNERS): remove me from some components 3 yıl önce
COMMITS.md docs: introduce conventional-commits (#1234) 4 yıl önce
CONTRIBUTING.md docs: add PR workflow info; move CONTRIBUTING to docs 4 yıl önce
COPYING docs: clear up licensing information 3 yıl önce
LICENSE.md docs: clear up licensing information 3 yıl önce
Makefile feat(crypto): Add Brian Gladman's implementation of GCM. 3 hafta önce
README.md chore(readme): add link to trezor.io KB disclosure article 1 yıl önce
SECURITY.md docs: use monospace for fingerprints 5 yıl önce
build-docker.sh build: differentiate between models for prodtest build 10 ay önce
create_monorepo.py chore: update branch name to main where its used 6 ay önce
poetry.lock build(deps): bump idna from 3.3 to 3.7 2 hafta önce
poetry.toml build(poetry): use new (parallel) installer 1 yıl önce
pyproject.toml feat: Remove pyblake2 1 ay önce
setup.cfg chore: upgrade style checkers 2 ay önce
shell.nix nix: unify ci/shell.nix and shell.nix 4 yıl önce

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.