Krux

This commit adjusts user-interface timing and sensitivity constants for the Krux hardware wallet: button debounce times are lowered, the allowed range for touch sensitivity is widened, and the swipe gesture threshold is reduced. These are usability/tuning changes, not security fixes. There is no indication in the commit or changelog that any vulnerability is being addressed.

This commit is a routine documentation update for the Krux project. It updates the website/docs to point users to a newer version of the Krux-Installer (v0.0.21 instead of v0.0.20), fixes some broken/typoed download links and file names, and reorganizes the macOS installation instructions. There is no code change and nothing in the commit suggests a security vulnerability or malicious behavior.

This is a one-line bug fix in Krux's QR code parser. A previous change accidentally broke Compact SeedQR support by trying to decode binary QR data as text before checking the format. The fix moves the decode step inside a try block so binary data is handled safely. There is no direct evidence this is a security vulnerability; it appears to be a functionality regression.

This commit fixes a shell script that sets the serial communication speed (baudrate) when flashing Krux firmware to certain hardware devices. Previously, the 'dock' device was missing from the list that should use a 1.5 Mbps baudrate, which could cause flashing to fail or be unreliable for that device. There is no security vulnerability here—it's a device compatibility/operational bug fix.

This commit fixes two typos in user-facing documentation. The instructions for verifying a downloaded file incorrectly included '.txt' in the filenames of the signature and checksum files. The patch removes '.txt' so the commands match the actual filenames produced by the project. There is no code change and no security vulnerability.

This commit fixes two typos in the user documentation for verifying a downloaded Krux installer. The instructions previously told users to run commands with an extra '.txt' in the filename, which would have caused the commands to fail because the actual signature and checksum files do not include '.txt'. This is a documentation-only correction with no code changes.

This commit only updates user documentation for the Krux installer. It removes per-platform verification instructions and replaces them with a single new page explaining how to verify the installer's authenticity and integrity. No source code, build scripts, or cryptographic checks in the project itself were changed.

This commit only updates user documentation for installing the Krux desktop installer. It removes per-platform instructions for verifying downloaded files and replaces them with a single shared verification page. There is no code change, no firmware change, and no change to how Krux devices validate firmware. The only security-relevant aspect is that the docs still tell users to check file signatures and hashes before installing the desktop app.

This commit only updates user documentation. It reorganizes troubleshooting instructions for flashing Krux firmware onto WonderMV and Yahboom devices and removes an unused snippet file. There are no code changes and no security implications.

This commit is a cosmetic user-interface cleanup. It changes how numbered word lists are formatted on screen so the numbers line up neatly and a missing space is restored. There is no security-relevant change.

This is a tiny UI bug fix in a Bitcoin hardware wallet project. When a user replaced a word in their recovery phrase, the on-screen confirmation prompt showed the wrong word number (it ignored which page of words was being viewed). The fix makes the displayed index match the actual word position. There is no security vulnerability here.

This commit fixes two functions in Krux's QR code handling so they can accept raw bytes as input, not just text strings. Previously, if a QR part arrived as bytes, the code would crash when it tried to search for text patterns like 'of' or check for a leading 'p'. The fix simply decodes bytes to text before processing. There is no direct evidence this was a security vulnerability, but a crash in QR parsing could in principle be triggered by a malformed QR and might affect availability or error handling.

This commit only refactors a single test file to make the tests less brittle and remove duplicated code. It does not change any production code, cryptographic logic, or user-facing behavior. There is no security issue here.

This commit is a cosmetic user-interface change. It splits a single line of text showing camera-captured entropy statistics into two lines so it fits better on small screens. No security-sensitive code, calculations, or behavior was altered.

This commit only changes a user-facing documentation file. It widens the suggested macOS command for finding a USB serial port from `ls /dev/cu.usbserial*` to `ls /dev/cu.usb*` so that more device names are matched. There is no code change, no security fix, and no vulnerability introduced.

This commit is a routine version bump from 25.11.beta0 to 25.11.beta1 and adds a new hardware device (WonderK) to the release build script. There are no security-relevant code changes.

This change makes QR codes easier to scan by converting the encoded text to uppercase letters. It is a usability improvement, not a security fix. There is no indication it addresses any vulnerability.

This commit fixes how Krux handles QR codes that contain raw binary data rather than plain text. Previously, some scanned binary QR codes may have been processed incorrectly because the firmware expected text strings. The change makes the device try to decode binary QR content as text when possible, and keep it as raw bytes when it cannot. This is a bug fix for handling certain binary-encoded QR codes, not a new security vulnerability.

This commit changes one line in the Kboot bootloader firmware to disable something called 'interactive mode.' The title suggests this is related to an issue with 'Embed Fire' hardware. Interactive boot modes can sometimes allow an attacker with physical access to interrupt the normal boot process, read memory, or load unauthorized code. Without the actual diff, we cannot see what was changed or confirm how serious it is.

This commit only updates documentation. It adds a hardware warning about the 'Embed Fire' device's touchscreen sometimes shifting in its case and some units not supporting high flash baud rates. It also rearranges and updates a list of community video tutorials. There are no code changes and no security fix or vulnerability.

This commit only updates a documentation table for hardware parts. It adds pixels-per-inch (PPI) values, reformats screen-resolution and camera labels, and replaces asterisks with 'x' in device dimensions. There is no code change and no security relevance.

This commit only updates user documentation about installing USB drivers on macOS and Windows. It changes the recommended macOS driver installation method to use the Homebrew package manager and makes minor formatting edits. There is no code change and no security issue.

This commit is a minor documentation update for Krux, a self-custody Bitcoin hardware wallet project. It updates the macOS troubleshooting instructions for users who have trouble flashing firmware due to missing CH34X USB drivers. There is no code change, no security fix, and no vulnerability introduced or patched.

This commit only adds documentation text telling macOS users how to install a missing USB driver (CH341) if they have trouble flashing their Krux device. There are no code changes, no bug fixes, and no security-related changes.

This change relaxes a safety rule in the Krux hardware wallet firmware. Previously, if a user scanned a BIP39 passphrase QR code containing non-English/non-ASCII characters (for example accented letters or symbols), Krux would block it with an error. Now it shows a warning and lets the user proceed anyway. The risk is that different wallet software may interpret those special characters slightly differently, so the user could end up with a different Bitcoin key than expected and potentially lose access to funds. The change is intentional and documented, not a hidden bug.