AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 19 Bitcoin

feat(core/emulator): report the exit kind and the boot args on exit [no changelog]

Public commit record

What the developer wrote

Authored by tychovrahe

85/100 · Strong
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>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
The short version

What changed, and why it matters

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.

Recommended action

No security action required. Treat as a normal emulator/test-infrastructure improvement. If reviewing for defense in depth, confirm trezor.bootargs is written only under the emulator profile directory and is not parsed implicitly by the emulator on startup.

Security signals we found

01

New file write to host filesystem: trezor.bootargs in profile directory

02

Emulator-only code paths; real hardware behavior unchanged

03

Removal of RSOD screen on bootloader-to-firmware jump in emulator

04

Standardization of emulator exit codes for test harness consumption

05

No cryptographic, authentication, or firmware verification changes

Risk score

Why this scored 19/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 9/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.