SeedSigner

This commit is a documentation and testing improvement for an existing safety cap in the PSBT parser. It does not change the cap's value or behavior; it explains why the cap exists (to stop a malicious PSBT from consuming unbounded memory), adds a test proving that hitting the cap does not corrupt the parse result, and clarifies that the cap was chosen based on a realistic large multisig transaction. There is no new vulnerability being fixed here, but the change makes the existing defense easier to understand and verify.

This commit removes a duplicated code branch that did the exact same thing twice in a row. The behavior of the program is unchanged; it is a minor cleanup with no security effect.

This commit is a performance optimization, not a security fix. It speeds up parsing of Bitcoin transaction files (PSBTs) on the slow Pi Zero hardware by avoiding repeated work: reading the transaction once instead of rebuilding it twelve times, using a direct fingerprint lookup instead of deriving a child key, and caching intermediate key derivations during parsing. The author explicitly states the parse output is unchanged and adds tests to prove the cached and uncached paths produce identical results.

This change improves how SeedSigner creates a new seed from camera noise. Before taking the final picture, it now requires 50 distinct, non-blank preview frames. This is a defensive hardening measure: it prevents a stuck, covered, or repeating camera from being mistaken for good randomness. It is not a fix for an active attack, but it reduces the chance that a hardware or environment problem produces a weak or predictable seed.

This commit fixes a user-interface bug in SeedSigner's 'image entropy' feature, where a user holding down a button could accidentally skip the live camera preview and the final photo review. Because the generated seed's randomness comes from the photo, skipping the review could let a user unknowingly accept a poor or unintended image. The patch now waits until the button is released before accepting the next press, and adds tests to confirm the behavior.

This commit fixes a bug in how SeedSigner creates and verifies Bytewords checksums, a format used to encode data (such as crypto wallet information) as readable words or compact strings. The checksum was sometimes output as 3 bytes instead of the required 4 bytes, which could cause other wallets or scanners to reject the encoded data. It also re-enables a previously disabled checksum verification, so corrupted data is now properly rejected instead of being silently accepted.

This commit adds a SECURITY.md file to the repository. It is purely a policy document that tells people how to privately report security bugs and what information to include. It does not change any code, fix any vulnerability, or introduce any new functionality.

This commit fixes a bug where selecting an existing seed during PSBT signing would crash because the code called a method (`get_seed`) that no longer exists. The fix uses the already-loaded list of seeds directly. The crash is a reliability issue, not a direct theft-of-funds vulnerability, but it could prevent a user from signing a transaction at a critical moment.

This commit only updates a submodule containing screenshots used for documentation or testing. There is no code change to the SeedSigner application itself, so it has no security impact on users.

This commit is a straightforward internal code cleanup: it replaces the use of numeric seed indexes (seed_num) with direct references to Seed objects throughout the user interface and tests. There is no security-relevant change; it is purely a refactoring to make the code clearer and avoid index-based lookups.

This commit is a large merge from the 'dev' branch into a documentation update branch. It primarily adds documentation, build/CI configuration, enclosure files, images, and project scaffolding. There is no code change that introduces a security vulnerability or fixes one. It is not a security-relevant patch.

This commit is a large merge pull request titled 'Resolves issue 555 - Improve UX navigating across DEL button (expanding it)'. The supplied diff shows only additions of project documentation, build workflows, Docker files, images, and templates — there are no code changes shown that modify the DEL button behavior or any application logic. Based on the visible materials, this appears to be a repository initialization or documentation/assets bulk addition rather than a functional security patch.

This commit fixes a small logic bug in SeedSigner, a hardware-wallet-like signing device. The code was checking whether a seed's fingerprint string was empty, but it should have been checking whether the seed has a passphrase. The bug could cause the app to skip computing or displaying the seed fingerprint at the wrong time, potentially confusing the user about which seed they are finalizing. There is no direct evidence in the commit that this is a security vulnerability, and no exploit path is described.

This commit only updates a submodule pointer for translation files. There is no code change visible, and nothing in the commit message or supplied materials suggests any security relevance.

This commit only updates a test file. It rewrites comments and adds two assertions to verify that backing out of seed word entry leaves the first word saved and clears the second word. There is no change to the actual application code that users run, so it cannot directly affect security.

This commit only fixes the indentation of a comment line so it is properly formatted as a code comment. No executable code, logic, or behavior was changed.

This commit only rewrites an inline code comment to describe the same back-button behavior more clearly. No actual code logic, function calls, or data handling changed.

This commit is a simple cleanup of automated tests. It merges two nearly identical test cases (one for 12-word seeds and one for 24-word seeds) into a single test that loops over both seed types. No production code was changed, and there is no security relevance.

This commit only adds a clarifying comment to existing code. It does not change any program behavior, fix a bug, or alter security logic. The comment explains that pressing the back button during seed phrase entry can mean either aborting entirely (on the first word) or returning to the previous word (on later words), and that aborting requires discarding the partially entered mnemonic.

This commit changes how the back button behaves during two seed-related screens. In the first screen, it simplifies the logic so that the pending mnemonic is only discarded when leaving from the first word. In the second screen, it removes the back-button handling entirely, meaning pressing back on the finalization screen no longer returns to the previous view. The commit message gives no security context, and the changes appear to be a UI-flow bugfix rather than a security fix, though removing back-button handling could affect user workflow or data persistence in subtle ways.

This commit simply deletes one automated test from the test suite. It does not change any production code that users interact with. By itself, removing a test does not create a security vulnerability, though it may reduce future confidence that a related feature still works correctly.

This commit only adds new automated tests to the SeedSigner project. It does not change any production code, so it cannot by itself introduce or fix a security vulnerability. The tests describe a previously fixed navigation bug where pressing BACK during seed entry could return the user to the wrong screen or leave internal flow state in an inconsistent state. Because the commit is limited to test code, its direct security relevance is low, though it documents behavior that could have had minor usability or state-consistency implications.

This commit fixes two minor user-interface navigation bugs in a Bitcoin seed-signer device app. In one screen, pressing the hardware back button after entering a mnemonic incorrectly dumped the user at the main menu instead of going back. In another screen, the back-button response was checked too late, after normal menu choices, which could make the back button behave oddly. These are usability fixes, not security fixes.

This commit replaces a shell command used to read the Raspberry Pi CPU serial number with safer built-in Python file reading. The old code ran the command 'cat /proc/cpuinfo | grep Serial' through the operating system shell, which is generally discouraged because it can be risky if any part of the command string is ever influenced by untrusted input. In this specific case, the command string was hardcoded and contained no user input, so the direct risk is low. The change is a defensive hardening improvement rather than a fix for an active vulnerability.

This commit simply adds the word '(beta)' to the Czech language label in the settings, matching how other unfinished translations are already labeled. It is a cosmetic/UI labeling change with no security relevance.