factorysetup: update context savings comment
What changed, and why it matters
This commit only updates a code comment to correct the estimated memory savings from using a static cryptographic context. No actual code behavior, logic, or security properties were changed.
No security action needed. This is a non-functional documentation-only change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The change is a single-line comment edit in src/rust/bitbox02-rust-c/src/secp256k1.rs. It replaces the outdated estimate of ‘35 kB’ saved by avoiding the secp256k1 signing precomputation table with a current estimate of ‘6.5 kB’ based on the 2 KiB signing table and updated library. The surrounding code, including the use of secp256k1_context_no_precomp and secp256k1_ecdsa_verify, is unchanged.
Changed components
src/rust/bitbox02-rust-c/src/secp256k1.rsInspect captured patch +1 / −1
### src/rust/bitbox02-rust-c/src/secp256k1.rs
@@ -51,7 +51,7 @@ pub extern "C" fn rust_secp256k1_verify(
};
// Signature verification does not need a dynamically allocated signing context. Using the
// static context also avoids linking the signing precomputation table into factory setup,
- // saving roughly 35 kB in the image.
+ // saving roughly 6.5 kB in the image with the 2 KiB signing table.
unsafe {
ffi::secp256k1_ecdsa_verify(
ffi::secp256k1_context_no_precomp,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.