Krux

This commit appears to be a routine maintenance update that bumps the MaixPy firmware submodule to a newer version and updates another component (uUC). The title describes it as a cleanup chore. No actual code changes are visible in the provided diff, and no security-related information is present in the commit message or materials.

This commit updates the build environment for the Krux project. It changes the Docker base image from an older Debian version (Bullseye with GCC 9.5.0) to a newer one (Bookworm with GCC 12) and updates the bundled 'embit' library. The commit message frames this as a routine maintenance chore needed to keep Python versions compatible. There is no indication in the commit itself that this fixes a security vulnerability.

This commit only adds documentation screenshots and text describing a vertical layout for the Stackbit 1248 metal backup format. It also updates a simulator script used to capture those screenshots. There is no code change that affects security.

This commit only updates the project's CHANGELOG.md file to document a new vertical layout option for the Stackbit 1248 backup display. It adds three lines of text describing a user-facing feature. There are no code changes, no configuration changes, and no security-relevant modifications.

This commit only adds and updates automated tests for a backup-screen layout feature called Stackbit. It does not change any production code, so it cannot introduce a security vulnerability or fix one.

This commit only adds translated text strings for two menu labels, 'Standard' and 'Vertical', used in the stackbit feature. It does not change any program logic, security checks, or data handling. There is no security relevance.

This commit adds new on-screen backup layout options for a Bitcoin hardware wallet feature called Stackbit 1248. It only changes how the wallet's seed phrase is drawn on the device display so users can physically punch it into a metal backup card. There is no security vulnerability visible in the change.

This commit only updates the project's .gitignore file to exclude common AI assistant configuration files (like CLAUDE.md, AGENT.md, .cursorrules, and folders such as .claude/). It does not change any executable code, build scripts, cryptographic logic, or user-facing behavior. There is no security relevance.

This commit is a user-interface polish change: it adds a new green-colored success message method and switches existing success messages from the default text color to green. There is no security-relevant behavior change.

This commit swaps out the pure-Python QR code encoding/decoding libraries used by the Krux hardware wallet for a new C module called uUR. The stated goal is faster scanning and lower memory use. The change touches code that handles Bitcoin wallet descriptors, seed phrases, and signed transactions (PSBTs). There is no direct evidence in the commit of a security vulnerability, but any rewrite of code that parses cryptographic data deserves careful review because a bug could in theory cause the wallet to misread a transaction or seed. The commit does not describe itself as a security fix.

This commit updates the Pillow image-processing library from version 12.1.1 to 12.2.0 in Krux's optional simulator dependencies. The change itself only bumps version numbers and lock-file hashes; it does not modify Krux application code. Pillow 12.2.0 is a routine maintenance release that fixes several bugs and security issues in image handling, so the update is generally beneficial. However, the commit message does not say which vulnerabilities are being addressed, and the diff provides no direct evidence of a specific security problem in Krux.

This commit removes a developer-only translation helper that relied on the 'translate' package, which in turn pulled in the 'lxml' XML-processing library. The stated goal is to reduce exposure to lxml, a large native-code dependency that has a history of security vulnerabilities. The change only affects development tooling and does not alter the actual Krux firmware or wallet code that end users run.

This commit removes the visual grid lines drawn on camera scans of TinySeed metal backup plates. It is a user-interface improvement to make the punched holes easier to see; it does not change security logic, cryptography, or data handling.

This commit is a routine version bump from 26.03.1 to 26.04.0 across three configuration/source files, plus adding '.claude' to the .gitignore file. There are no code changes that affect security, functionality, or user behavior.

This commit fixes four security weaknesses in Krux, a Bitcoin hardware-wallet project. The changes prevent: (1) encrypted backups from declaring zero or very low password-stretching effort, which would make them easy to brute-force; (2) multi-signature wallet descriptors from silently accepting multiple cosigners whose identity cannot be verified; (3) a malicious or corrupted SD card from tricking the file manager into leaving its intended folder; and (4) repeated wrong password attempts on encrypted backups by adding growing delays between attempts. All four are hardening fixes rather than a single critical vulnerability.

This update fixes a security hole in how Krux reads its settings file from an SD card or flash storage. Before, an attacker with physical access could put an abnormally large or oddly shaped settings.json file on the card and crash or confuse the device. Now the device refuses to load any settings.json larger than 8 KB and rejects files whose contents are not a JSON object, falling back to safe default settings instead.

This commit fixes two denial-of-service weaknesses in Krux, a Bitcoin hardware-wallet firmware. First, it caps how much data can come out of compressed (deflated) QR codes and encrypted backups, preventing a maliciously crafted 'zip bomb' from exhausting the device's memory. Second, it rejects QR-code part counts that are zero or absurdly high, preventing an attacker from tricking the wallet into reserving unbounded memory while scanning multi-part QR codes.

This commit adds a warning screen to Krux's message-signing feature when the user is about to sign a raw 32-byte hash or a 64-character hex string. Previously, the device would silently treat such inputs as already-hashed values and sign them directly. Because a Bitcoin transaction's signature hash (sighash) is also a 32-byte value, an attacker could trick a user into signing what looks like a harmless message but is actually a transaction hash, effectively authorizing a transaction. The fix asks the user to confirm before proceeding.

This update fixes two security issues in Krux, a Bitcoin signing device. First, it prevents the device from crashing when calculating fees for transactions that send no regular bitcoin (only data outputs like OP_RETURN). Second, it now rejects invalid multisig wallet setups where zero signatures are required or where more signatures are required than keys exist, which could otherwise allow unauthorized or impossible spending rules.

This commit removes a single line of Python code that could never run. The removed line sat immediately after a `while True:` loop that only exits by returning from the function, so execution could never reach it. It is a harmless cleanup with no security effect.

This commit removes two unused duplicate text strings that listed hexadecimal and octal digits from a login-related source file. There is no functional code change, no bug fix, and no security relevance visible in the diff.

Krux is a small, open-source Bitcoin signing device (hardware wallet). This commit fixes a security flaw where the device would sign transactions even if the sender asked it to use unusual Bitcoin signature modes—specifically SIGHASH_NONE, SIGHASH_SINGLE, or ANYONECANPAY. Those modes can let someone else change where the money goes after the device has already signed, which could be abused to steal funds. The fix makes the device refuse to sign any PSBT (the file format used to pass a transaction around) that contains those non-standard modes. The project labels this as a security fix for an external audit finding.

This commit only updates three version strings from a beta release to a stable release. It changes no code logic, no security settings, and no dependencies. There is nothing here that affects security.

This commit simply adds two new hardware device targets (Embed Fire and WonderK) to the project's automated build script. It is a routine configuration change with no security relevance.

This commit only updates the title line of the project's CHANGELOG file, changing the placeholder version and date to a concrete release version. It does not modify any code, configuration, or documentation that affects how the software behaves or how secure it is.