SeedSigner

This commit simply moves a block of existing code (the git shell command helpers) to a different location in the same file and renames a couple of test methods. No behavior changes, no security fixes, and no new vulnerabilities are introduced.

This commit is purely a code cleanup and test expansion. It renames internal helper methods in the version utility to be clearer (for example, changing `_get_version_name_from_env_var` to `_get_version_name_from_seedsigner_os_env_var`), reorganizes comments, and adds new tests to keep test coverage at 100%. There is no change to user-facing behavior, no fix for a bug, and no security-related change.

This commit restores a helper function that lets the project’s screenshot generator temporarily override version information shown in screenshots. The function is decorated so it cannot run on the actual SeedSigner OS device. It only affects display text used in documentation screenshots, not private keys, seeds, or transaction logic.

This commit is a routine internal refactor of how the app reads its own version information (version name, fork, timestamp, commit hash). It consolidates singleton setup, renames constants and methods, adds GitHub Actions CI detection, and expands unit tests to reach 100% code coverage. There is no direct evidence in the commit that this fixes a security vulnerability or introduces a new attack path. The changes are mostly about making version reporting more reliable and testable.

This commit is mostly a routine code cleanup and test expansion for how SeedSigner reports its software version. It renames a decorator, adds more tests, improves error handling when files are missing, and fixes a timestamp formatting bug when checking GitHub releases. There is no direct evidence in the commit that this fixes an active security vulnerability, but it does reduce risky behavior such as silently swallowing errors and making unverified shell calls in some contexts.

This is a large code refactor that changes how SeedSigner detects and displays its software version. It replaces a simple version reader with a more complex singleton system that reads git state, environment variables, and a JSON file. The changes are mostly about version reporting and do not appear to alter how private keys, seeds, or Bitcoin transactions are handled. There is no clear security bug visible in the diff, but the refactor introduces new code paths that touch files and shell commands, which always carry some risk of mistakes.

This commit fixes a bug in how SeedSigner determines and reports its software version. Previously, the version was set once and could be left blank or stale in certain build situations. The patch makes version detection more reliable by trying multiple sources: an environment variable, the current Git branch, the latest Git tag, and finally the short commit hash. There is no direct evidence this is a security fix, but reliable version reporting helps users and developers confirm they are running the expected software.

This commit adds a single debug print statement that displays the value of an environment variable used during the build process. It does not change how the software works, does not introduce a security flaw, and does not affect end-user security. It is a routine development/debugging change.

This commit simply renames a method from get_last_edit to get_last_edit_timestamp and updates the places that call it and test it. There is no security issue here—just a cleanup to fix a naming mismatch (the caller was already using a name that did not exist).

This commit removes a leftover debug print statement and changes how the software figures out its own version name by asking the Git tool directly instead of relying on a pre-existing file. The change itself is not a security fix, but it removes a minor information leak (the hostname) and avoids a build-time dependency on a generated file. There is no evidence this was reported as a security issue or credited to a researcher.

This commit changes how the SeedSigner software figures out its own version number when it cannot read version info from the local git repository. Instead of immediately giving up, it now checks whether it is running inside GitHub Actions and, if so, uses environment variables provided by GitHub to determine the version. There is no security issue visible in this change.

This commit changes how SeedSigner records its software version and build timestamp. It now reads a version name from an environment variable used by SeedSigner OS and forces the last-edit timestamp to UTC. These are build-process improvements, not fixes for an active security vulnerability. The only security-relevant aspect is a small hardening of how external shell commands and environment input are handled.

This commit changes how SeedSigner records the 'last edit time' in its version.json file. Previously it scanned all source files for the most recent modification time. Now it runs a git command to use the most recent commit timestamp. The main concern is that it uses os.popen(), which executes a shell command, and does not validate the output. In normal use this is benign, but if an attacker can control the working directory or git executable, it could become a command-injection or misleading-metadata issue. There is no direct evidence this is being exploited.

This commit is a small code-quality improvement that cleans up how a file path is constructed. It uses a standard function (os.path.normpath) to remove redundant '..' segments from a path and prints the actual resolved path instead of a hardcoded string. There is no direct evidence this fixes an exploitable security vulnerability.

This commit removes a hard-coded version number from the SeedSigner software and instead reads the version from a generated file or git metadata. It also adds a debug print statement that exposes the device's hostname setting to standard output. There is no direct security vulnerability in the diff itself, but the change makes version reporting depend on build-time files and local git state, and it leaks an internal configuration value in logs or console output.

This commit is a small code cleanup in SeedSigner's version helper. It extracts a repeated file-path calculation into a shared method and updates a comment about where the version file is written. There is no security-relevant change: the same file is read/written, the same JSON parsing occurs, and no new inputs or trust decisions are introduced.

This commit adds a helper that can write the project's version number and last source-edit time into a small JSON file. It is a build/infrastructure change with no apparent security relevance.

This commit only changes test files. It removes direct assignments to a shared Settings.HOSTNAME variable inside tests and replaces one with a temporary mock. This prevents test runs from accidentally leaving the simulated device hostname in an unexpected state for later tests. There is no change to the actual SeedSigner application or its security behavior.

This commit changes how the app finds its own source-code folder so it works correctly in automated build environments. The old code assumed the project path always contained the literal text '/src' and used string splitting, which could fail or behave unexpectedly on some systems. The new code walks up a fixed number of parent directories. There is no direct security vulnerability here, but the old approach could have produced wrong paths in unusual environments.

This commit simply moves existing version-checking code from one file to a new dedicated helper file. It is a routine code cleanup with no visible security implications.

This commit is a small code cleanup that changes how the app finds the project root directory. It replaces a method based on the current working directory with one based on the location of the source file itself. There is no security issue visible in the change.

This commit only changes how a settings menu screenshot is generated for documentation. It adds a way to pre-select a specific menu button so the screenshot can show the bottom of the settings list. There is no security-relevant change to user-facing behavior, cryptography, or private data handling.

This is a one-line tightening of a string comparison. The code previously accepted a tag file's commit hash if it merely began with the same characters as the git reference; now it requires an exact match. This prevents a partial-prefix match from being treated as a valid tag, which could in theory cause the wrong software version tag to be displayed or selected. There is no direct evidence this is exploitable for harm, and the commit message does not describe it as a security fix.

This commit adds a new 'Version' menu in Settings and updates the opening splash screen to show the software version. It is a straightforward user-interface feature with no security relevance.

This commit is a routine UI enhancement for a Bitcoin hardware wallet project. It renames an internal method, adds a helper that finds the most recently modified source file, and displays that timestamp on the version/about screen. There is no security-relevant change.