Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Security candidatefeat(trezorlib): run a bootloader firmware update in the background [no changelog]by tychovrahe · b3af0805 · Oct 20, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · tychovrahe
feat(trezorlib): run a bootloader firmware update in the background [no changelog]
An update onto installed firmware waits for an on-screen confirmation, so it has to run beside the test that confirms it.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This commit is a small internal test-utility change. It adds a configurable timeout and a background-thread helper to the Python test library that emulates a Trezor bootloader during firmware updates. There is no indication it fixes a security bug or introduces a vulnerability; it appears to be a test-infrastructure convenience feature.
STOP_AND_CONNECT lands the bootloader on the host-waiting screen, the one that polls the wire.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trust
AI analysis · Informational 15/100
This commit simply adds a new named option in the Trezor Python library that tells a Trezor bootloader to stop at the 'wait for host' screen. There is no bug, no vulnerability, and no security fix visible in the change.
- Remove static_private_key from handshake state. Pass it as a parameter where needed instead.
[no changelog]
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 29/100
This commit changes how a secure-handshake library (used to set up encrypted connections) stores sensitive keys. Previously, the long-term private key, public key, and pre-shared key were copied into a handshake state structure at initialization and kept there for the whole handshake. Now they are passed only to the specific functions that actually need them. This reduces the window during which those secrets sit in memory inside the handshake object, which is a defensive hardening improvement rather than a fix for an active bug. There is no claim by the vendor that this resolves a reported security vulnerability.
Security candidatetest(core): record bootloader UI fixtures for the install tests [no changelog]by tychovrahe · 596afe0a · Oct 20, 2026 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · tychovrahe
test(core): record bootloader UI fixtures for the install tests [no changelog]
T2T1, T3B1, T3T1 and T3W1.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
87/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
update trust
AI analysis · Informational 15/100
This commit only adds pre-recorded test snapshots (called 'fixtures') for bootloader firmware-install tests on four Trezor device models. It does not change any executable code, security logic, or user-facing behavior. There is no security issue.
Install of a trusted image on an empty device (no confirmation, reboot, storage erased), upgrade of installed firmware (confirmation, reboot, seed kept) and boot with the image preloaded (jump, command cleared, storage retained). The confirm helper is shared with the wipe test; on Caesar a confirmation with an info page confirms with both buttons.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This commit only adds and reorganizes automated test code for the Trezor bootloader. It does not change any firmware, bootloader, or production code. The new tests verify normal, expected behavior: installing firmware on an empty device, upgrading existing firmware with user confirmation, and booting preloaded firmware. There is no security-relevant code change here.
Security candidatefeat(trezorlib): accept a bootloader run that ends before the debug link answers [no changelog]by tychovrahe · a5fd7788 · Oct 20, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · tychovrahe
feat(trezorlib): accept a bootloader run that ends before the debug link answers [no changelog]
A boot into trusted firmware takes the bootloader no time at all, so the process can be gone before the readiness probe gets an answer. That is an outcome, not an error: start() returns without a context and wait_exit() reports it.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This commit changes an internal test helper in Trezor's Python library so that when a simulated bootloader finishes very quickly (because it immediately boots into trusted firmware), the test code treats that as a normal result instead of throwing an error. It is a testing/QA reliability fix, not a security patch for user-facing code.
Security candidatetest(core): synthesize dev-key signed firmware images for the bootloader tests [no changelog]by tychovrahe · ac1e2c39 · Oct 20, 2026 · 3 filesMessage 95 · StrongInformational 19Details
Commit message · tychovrahe
test(core): synthesize dev-key signed firmware images for the bootloader tests [no changelog]
make_firmware() builds an image from a checked-in dev vendor header, a firmware header with the requested version and model, and filler code, rehashed and signed the way headertool does it. On secmon models a signed TSEC image is embedded at the aligned offset. The runner fills the model specifics in from the emulator's -p output.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 19/100
This commit adds test-only code that creates fake Trezor firmware images signed with the project's public development keys. The images are used only in automated bootloader tests and never contain real firmware code. It does not change any production bootloader, firmware, or signing process, and it does not introduce a vulnerability in shipped devices.
Security candidatefeat(core/bootloader_emu): report secmon verification and code alignment with -p [no changelog]by tychovrahe · b0450b54 · Oct 20, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · tychovrahe
feat(core/bootloader_emu): report secmon verification and code alignment with -p [no changelog]
A test harness building firmware images for the emulator needs to know whether the bootloader expects a secure monitor inside the image and at which alignment it looks for it.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustdefensive validationboot or update path
AI analysis · Informational 15/100
This commit adds diagnostic output to the Trezor bootloader emulator. When run with a special flag, it now prints two extra pieces of information: whether the bootloader expects a 'secure monitor' component in firmware images, and what memory alignment it requires for firmware code. This is purely a testing/debugging convenience for the emulator and does not change how real devices verify or load firmware.
A suite with one emulator run per test, recorded from the first frame when UI fixtures are on, and a first test: a host wipe of an empty device, confirmed on screen, checked through the exit record.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This commit only adds new automated test code for the Trezor bootloader emulator. It introduces a test suite, supporting fixtures, documentation, and Makefile targets to run bootloader tests. There is no change to firmware, bootloader, or production code, and no security fix or vulnerability is present in the diff.
test(core): record bootloader UI fixtures [no changelog]
T2T1, T3B1, T3T1 and T3W1.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
87/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
update trust
AI analysis · Informational 15/100
This commit only adds new test fixture hashes to a JSON file used for automated UI testing of the bootloader. It records expected screen outputs for a device-wipe test on four Trezor models. There are no code changes, no user-facing behavior changes, and no security fix or vulnerability present.
Security candidateci: run the bootloader emulator tests [no changelog]by tychovrahe · 4c64bb7b · Oct 20, 2026 · 3 filesMessage 95 · StrongInformational 15Details
Commit message · tychovrahe
ci: run the bootloader emulator tests [no changelog]
The job builds its own emulator with the development keys and debuglink, runs the suite with UI fixtures and reports through the ui-report action. The PR comment and the fixture updater know the job.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trust
AI analysis · Informational 15/100
This commit adds a new automated test job to the project's continuous integration (CI) pipeline. It builds and runs bootloader emulator tests for several Trezor hardware wallet models and updates helper scripts so the new test job is included in pull-request reports and fixture updates. There is no change to the firmware code that runs on user devices, no fix for a vulnerability, and no security-relevant behavior change.
feat(trezorlib): decode and build bootloader boot arguments [no changelog]
BootArgs mirrors bootargs.h and the trezor.bootargs file the unix build writes on exit: the boot command with typed views of its arguments (upgrade hash, wipe info, post-mortem) and builders for test inputs.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trust
AI analysis · Informational 15/100
This commit adds a new Python helper file inside the Trezor library that can read and write a small data file used by the Trezor emulator and bootloader. It is purely a test/development utility for formatting boot arguments (for example, telling the device to install an upgrade, wipe itself, or show a crash screen). There is no change to the device firmware, no user-facing feature, and no security fix or vulnerability introduced in this code.
Security candidatefeat(trezorlib): add a bootloader emulator wrapper for tests [no changelog]by tychovrahe · e9f64d6d · Oct 20, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · tychovrahe
feat(trezorlib): add a bootloader emulator wrapper for tests [no changelog]
One BootloaderEmulator is one run of bootloader-emu with explicit startup parameters. Its test context drives the screen over the debug port and talks to the bootloader over the wire port; wait_exit() reports the exit kind, the boot args left behind and whether storage survived.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This commit adds a new Python test helper that wraps the Trezor bootloader emulator so automated tests can start it, interact with it, and check how it exits. It is purely test infrastructure code and does not change the bootloader, firmware, or any user-facing behavior. There is no security-relevant change to the product itself.
Security candidatefeat(core/bootloader_emu): print the model and flash layout with -p [no changelog]by tychovrahe · ee21059c · Oct 20, 2026 · 2 filesMessage 95 · StrongInformational 15Details
Commit message · tychovrahe
feat(core/bootloader_emu): print the model and flash layout with -p [no changelog]
A test harness needs the storage-area offsets to judge the flash file after a run; print them as JSON instead of keeping a per-model table on the host side.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This change adds a new command-line option (-p) to the Trezor bootloader emulator that prints the device model and flash storage layout as JSON, then exits. It is a developer/testing convenience feature and does not change how real hardware wallets work or how secrets are protected.
Security candidatefix(core/bootloader_emu): write the storage marker after parsing the options [no changelog]by tychovrahe · 4e1aea73 · Oct 20, 2026 · 1 fileMessage 85 · StrongInformational 19Details
Commit message · tychovrahe
fix(core/bootloader_emu): write the storage marker after parsing the options [no changelog]
The marker that simulates non-empty storage was written before argv was parsed, so even an informational invocation such as -h modified the flash file.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 19/100
This change fixes a minor bug in the Trezor bootloader emulator, a software simulation tool used for development and testing. Previously, simply running the emulator with a help flag (-h) would write a marker to a simulated flash file, even though the user only wanted information. Now the marker is written only after command-line options are parsed, so informational invocations no longer touch the flash file. This is a correctness fix for a development tool, not a fix for a vulnerability in real Trezor hardware wallets.
Security candidatefeat(core/bootloader_emu): record screen refreshes from startup with -r [no changelog]by tychovrahe · 04f276cd · Oct 20, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · tychovrahe
feat(core/bootloader_emu): record screen refreshes from startup with -r [no changelog]
Boot-path screens appear before any host can connect and send DebugLinkRecordScreen, so the recording has to start from argv.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This commit adds a new command-line option to the Trezor bootloader emulator that lets developers record every screen refresh as a PNG image. It is a debugging/testing feature for the emulator only and does not change how real hardware wallets behave. There is no indication this is a security fix or that it introduces a security problem.
Security candidatefeat(core/bootloader_emu): add -W and -R for the wipe and RSOD boot commands [no changelog]by tychovrahe · 439b921a · Oct 20, 2026 · 1 fileMessage 85 · StrongInformational 19Details
Commit message · tychovrahe
feat(core/bootloader_emu): add -W and -R for the wipe and RSOD boot commands [no changelog]
-R exists only on models that define USE_BOOTARGS_RSOD; the others ignore the command.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 19/100
This change adds two new command-line options to the Trezor bootloader emulator, a software-only testing tool used by developers. The -W option simulates a device wipe request, and -R simulates a red-screen error display. These options only affect the emulator and do not change how real Trezor hardware behaves. There is no indication this fixes or introduces a security vulnerability in actual devices.
Security candidatefeat(core/bootloader_emu): take the boot command from a file with -B [no changelog]by tychovrahe · 5f1f81d0 · Oct 20, 2026 · 3 filesMessage 95 · StrongInformational 15Details
Commit message · tychovrahe
feat(core/bootloader_emu): take the boot command from a file with -B [no changelog]
Loads a file in the format a previous run wrote to trezor.bootargs, so a test can hand one run's exit record to the next run explicitly.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This change adds a new command-line option (-B) to the Trezor bootloader emulator so it can read a boot command and arguments from a file. It is a testing/development convenience feature for the emulator only and does not appear to introduce a security vulnerability. The file is read in a fixed-size binary format and passed to the existing bootargs_set function.
Security candidatefeat(core/emulator): report the exit kind and the boot args on exit [no changelog]by tychovrahe · 1b4ef941 · Oct 20, 2026 · 4 filesMessage 85 · StrongInformational 19Details
Commit message · tychovrahe
feat(core/emulator): report the exit kind and the boot args on exit [no changelog]
Every reboot_* path of the unix build now sets the boot command the hardware would pass to the next stage, writes the command and its arguments to trezor.bootargs in the profile directory and exits with a code that names the kind of exit: 2 quit, 3 reboot, 10 jump, 11 power off, 12 halt after RSOD. TREZOR_EMULATOR_FAST_EXIT=1 skips the delays that let a human read the screen first.
The bootloader emulator no longer shows its own "BOOTLOADER EXIT" RSOD on the jump to firmware; the storage state is readable from trezor.flash. The file is output only and never read back implicitly.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 19/100
This commit changes only the Trezor software emulator (the desktop test version, not real hardware). It makes the emulator write its next-boot instructions to a file named trezor.bootargs and exit with specific numeric codes so automated tests can tell what happened. It does not change how real Trezor devices work, store secrets, or verify firmware. The file is only written, never automatically read back in. There is no indication this fixes or introduces a security vulnerability.
Security candidatechore(core/bootloader): run the firmware check only for debuglink messages that need it [no changelog]by tychovrahe · fc93d6f6 · Oct 20, 2026 · 1 fileMessage 85 · StrongInformational 19Details
Commit message · tychovrahe
chore(core/bootloader): run the firmware check only for debuglink messages that need it [no changelog]
fw_check hashes the whole image. Only Initialize and GetFeatures report on it, so run it there, fresh for each message, instead of for every debug packet. The debuglink is now also polled during an upload, when the image is incomplete anyway.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 19/100
This is a small bootloader performance and robustness tweak. Previously, the bootloader computed a hash of the entire firmware image for every debuglink message, even when that hash wasn't used. Now it only computes the hash for the two message types that actually report it (Initialize and GetFeatures), and it recomputes it fresh for each such message. The change also avoids hashing during firmware uploads when the image is incomplete. There is no direct security fix here, but it removes a potential source of inconsistent or stale state and reduces unnecessary work.
fix(core/bootloader): answer unknown debuglink messages with Failure [no changelog]
Every unhandled message was acknowledged with Success, so a host could believe a WipeDevice or DebugLinkReseedRandom over the debug link had been carried out.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Moderate 60/100
A bug in the Trezor bootloader's debug communication channel made it reply 'Success' to every unrecognized command. This meant a host computer sending a command such as WipeDevice or DebugLinkReseedRandom over the debug link could be tricked into thinking the device had actually carried out the action, even though it had not. The fix changes the bootloader to reply with a proper 'unknown message' failure instead.
fix(core/bootloader): honour refresh_index in DebugLinkRecordScreen [no changelog]
The index was ignored and always 0, so recordings taken across an emulator restart within one test overwrote each other.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trustboot or update path
AI analysis · Informational 20/100
This is a tiny bug fix in the Trezor bootloader's testing/debugging helper. A screen-recording feature used only during automated emulator tests was ignoring a 'refresh index' number, so multiple recordings taken after emulator restarts would overwrite each other. The change makes the code use the provided index. It is not a security vulnerability affecting real devices or users.
Security candidatefix(core/bootloader): service the debuglink in the click and upload loops [no changelog]by tychovrahe · 9776b28a · Oct 20, 2026 · 2 filesMessage 85 · StrongInformational 18Details
Commit message · tychovrahe
fix(core/bootloader): service the debuglink in the click and upload loops [no changelog]
The click-to-continue boot screen and the firmware upload loop polled only their own input, so a DebugLinkGetState sent while either was on screen stayed unanswered until the next UI loop. Poll the debug interface there too.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 18/100
This commit fixes a bootloader responsiveness issue for automated testing: when the Trezor bootloader was showing the 'click to continue' screen or receiving a firmware image, it ignored DebugLink requests until the user or host did something else. The change makes those loops also poll and answer the debug interface immediately. DebugLink is a test-only feature, not present in production devices, so this is a testing/QA fix rather than a user security vulnerability.
Security candidatefix(core): add missing colons in Tron flowsby Michal Kazda · 1d853c95 · Oct 20, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda
fix(core): add missing colons in Tron flows [no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit is a tiny UI text formatting fix for Tron cryptocurrency transaction screens on Trezor devices. It adds missing colons to the labels shown next to the amount and fee values, matching the formatting already used for other labels. There is no security issue here.
Security candidatechore: bump versionsby Jakub Janků · de7bc335 · Oct 20, 2026 · 11 filesMessage 55 · ThinInformational 15Details
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
This commit only updates version numbers and translation metadata. It does not change any code that handles security, cryptography, user data, or device behavior. There is nothing here that introduces or fixes a security issue.