AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 16 Bitcoin

chore(core): adapt to mldsa-native v2.0.0

Public commit record

What the developer wrote

Authored by M1nd3r

95/100 · Strong
chore(core): adapt to mldsa-native v2.0.0

- Removed `siglen` from signing/verification.
- Signature size is now checked in prodtest before signature verification.
- Added `src/polyvec_lazy.c` to be compiled.
- Renamed `MLD_CONFIG_API_PARAMETER_SET` to `MLD_CONFIG_PARAMETER_SET`.

[no changelog]
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
The short version

What changed, and why it matters

This is a routine maintenance update that adapts Trezor's firmware code to version 2.0.0 of an external cryptographic library called mldsa-native. It mainly renames configuration constants, removes an unnecessary signature-length parameter from function calls, and adds a signature-size check in the production-test verification path. There is no direct evidence in the commit that this fixes an active security vulnerability.

Recommended action

Treat as a dependency/API-sync patch. Review whether the new mldsa-native v2.0.0 release contains any security fixes or behavioral changes that should be noted, since the commit itself does not disclose security relevance. Validate that the added sig_size check in prodtest covers all verification entry points and that mldsa44_verify still enforces the correct fixed signature size internally.

Security signals we found

01

Signature-size validation added in prodtest verify_signature path

02

API migration to new major version of external cryptographic library

03

Static assertions updated for renamed parameter-set macro

04

No changelog entry provided by vendor

Risk score

Why this scored 16/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 7/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.