In the ML-DSA signature driver, in addition to supporting the standard private key representation (just the seed), support a custom format that contains the expanded private key and the expanded public key.
We have a short-term business case for this through the multipart API, but in the medium term we also want it through the one-shot API, so we might as well do both.
Test this both through direct calls to the driver and through dispatch. (No library change is expected for dispatch.)
Prerequisites: #635
Enhances: #771 (when we have both dispatch-to-multipart and expanded key support, test dispatch to multipart with expanded key).
Follow-ups: the core actually taking advantage of this. We don't have a full architectural design yet. Interface discussion in ARM-software/psa-api#308.
In the ML-DSA signature driver, in addition to supporting the standard private key representation (just the seed), support a custom format that contains the expanded private key and the expanded public key.
We have a short-term business case for this through the multipart API, but in the medium term we also want it through the one-shot API, so we might as well do both.
Test this both through direct calls to the driver and through dispatch. (No library change is expected for dispatch.)
Prerequisites: #635
Enhances: #771 (when we have both dispatch-to-multipart and expanded key support, test dispatch to multipart with expanded key).
Follow-ups: the core actually taking advantage of this. We don't have a full architectural design yet. Interface discussion in ARM-software/psa-api#308.