What changed, and why it matters
This commit simply adds official release signatures and build attestation files for firmware version 9.23.2. It does not change any source code, fix any bug, or alter any behavior of the BitBox02 device. There is nothing in the commit that introduces or addresses a security issue.
No security action required; this is a routine release attestation commit. If reviewing the v9.23.2 firmware for security issues, examine the actual source-code changes between v9.23.1 and v9.23.2 rather than this release metadata commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit creates four new files under releases/firmware-v9.23.2/ and releases/firmware-btc-v9.23.2/: assertion.txt files containing a signed statement that a firmware binary built from git commit e968d12544e16d6ae4305cf4ed8e917d20697dae yields a specific SHA-256 hash, plus detached GPG signatures (assertion-benma.sig). No source code is modified.
Changed components
releases/firmware-v9.23.2/assertion.txtreleases/firmware-v9.23.2/assertion-benma.sigreleases/firmware-btc-v9.23.2/assertion.txtreleases/firmware-btc-v9.23.2/assertion-benma.sigInspect captured patch +16 / −0
diff --git a/releases/firmware-btc-v9.23.2/assertion-benma.sig b/releases/firmware-btc-v9.23.2/assertion-benma.sig
new file mode 100644
index 0000000..4032490
Binary files /dev/null and b/releases/firmware-btc-v9.23.2/assertion-benma.sig differ
diff --git a/releases/firmware-btc-v9.23.2/assertion.txt b/releases/firmware-btc-v9.23.2/assertion.txt
new file mode 100644
index 0000000..5a653c6
--- /dev/null
+++ b/releases/firmware-btc-v9.23.2/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.23.2
+git commit hash e968d12544e16d6ae4305cf4ed8e917d20697dae
+
+resulted, at the time of signing, in a firmware binary file with the following sha256sum:
+
+7476febce1e914f52c9d1c7ce860823cf5e965bded76eb420982c55f8dbd9dfe
diff --git a/releases/firmware-v9.23.2/assertion-benma.sig b/releases/firmware-v9.23.2/assertion-benma.sig
new file mode 100644
index 0000000..d82870e
Binary files /dev/null and b/releases/firmware-v9.23.2/assertion-benma.sig differ
diff --git a/releases/firmware-v9.23.2/assertion.txt b/releases/firmware-v9.23.2/assertion.txt
new file mode 100644
index 0000000..f3ec4bf
--- /dev/null
+++ b/releases/firmware-v9.23.2/assertion.txt
@@ -0,0 +1,8 @@
+By signing this file, the signer confirms that the firmware binary built from:
+
+git tag firmware/v9.23.2
+git commit hash e968d12544e16d6ae4305cf4ed8e917d20697dae
+
+resulted, at the time of signing, in a firmware binary file with the following sha256sum:
+
+473f0f110ffa969444e3b37dd1399a6fac8463e8cbaed267af88f92f1c2c8281
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.