What changed, and why it matters
This commit adds release artifacts for BitBox02 firmware version 9.24.0. It contains two signed statements (assertions) confirming that building the source code at a specific git tag produces a firmware binary with a known SHA-256 hash. There is no code change, no bug fix, and no security-related content in the commit itself.
No security action required. Treat as routine release metadata. Users who verify reproducible builds can compare their locally built firmware hash against the published SHA-256 in assertion.txt and validate the signature.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit introduces four new files under releases/firmware-v9.24.0/ and releases/firmware-btc-v9.24.0/: assertion.txt files stating the git tag, commit hash (ca5877dbc61bde4bfc643da6028aa9e3c077e62c), and expected SHA-256 of the resulting binary, plus detached signatures (assertion-benma.sig). This is a standard reproducible-build attestation/release signing procedure. The diff shows only additions of release metadata and binary signature files.
Changed components
releases/firmware-v9.24.0/assertion.txtreleases/firmware-v9.24.0/assertion-benma.sigreleases/firmware-btc-v9.24.0/assertion.txtreleases/firmware-btc-v9.24.0/assertion-benma.sigInspect captured patch +16 / −0
diff --git a/releases/firmware-btc-v9.24.0/assertion-benma.sig b/releases/firmware-btc-v9.24.0/assertion-benma.sig
new file mode 100644
index 0000000..e9f75e5
Binary files /dev/null and b/releases/firmware-btc-v9.24.0/assertion-benma.sig differ
diff --git a/releases/firmware-btc-v9.24.0/assertion.txt b/releases/firmware-btc-v9.24.0/assertion.txt
new file mode 100644
index 0000000..9aef589
--- /dev/null
+++ b/releases/firmware-btc-v9.24.0/assertion.txt
@@ -0,0 +1,8 @@
+By signing this file, the signer confirms that the firmware binary built from:
+
+git tag firmware-btc-only/v9.24.0
+git commit hash ca5877dbc61bde4bfc643da6028aa9e3c077e62c
+
+resulted, at the time of signing, in a firmware binary file with the following sha256sum:
+
+eea1dce4d281b557e8034ffe3fac8ba24432e2c1b583b6038cb8be730e93d7c3
diff --git a/releases/firmware-v9.24.0/assertion-benma.sig b/releases/firmware-v9.24.0/assertion-benma.sig
new file mode 100644
index 0000000..3d8d4f3
Binary files /dev/null and b/releases/firmware-v9.24.0/assertion-benma.sig differ
diff --git a/releases/firmware-v9.24.0/assertion.txt b/releases/firmware-v9.24.0/assertion.txt
new file mode 100644
index 0000000..3359b0f
--- /dev/null
+++ b/releases/firmware-v9.24.0/assertion.txt
@@ -0,0 +1,8 @@
+By signing this file, the signer confirms that the firmware binary built from:
+
+git tag firmware/v9.24.0
+git commit hash ca5877dbc61bde4bfc643da6028aa9e3c077e62c
+
+resulted, at the time of signing, in a firmware binary file with the following sha256sum:
+
+41f1053ecdf2edc02834408f5cef0cd3d685913f3846619fbbbfa29b0461d9bc
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.