On 03-Sep-26 9:26 AM, Sucharitha Sarananaga wrote:
The existing asymmetric capability structure reports generic modulus length and hash algorithm support, but it cannot describe RSA-specific parameters required by OAEP and PSS. RSA operations may support different padding schemes and MGF1 hash algorithms independent of the primary hash algorithm. Applications currently have no standard way to discover these capabilities from a PMD. Add rsa_capa to report RSA modulus length, supported padding schemes, and MGF1 hash algorithms. Keep hash_algos for reporting primary digest support. Also clarify that the generic modlen field applies to other modulus-based transforms such as MODEXP, MODINV, DH, and DSA. RSA-PSS signing also normally generates its salt internally, so the same message never produces the same signature twice, making it impossible to validate against fixed test vectors (e.g. ACVP/CAVP SigGen). Add pss_explicit_salt to rsa_capa so a PMD can advertise support for an application-supplied PSS salt, and add the corresponding pss_salt field to rte_crypto_rsa_op_param to carry those bytes per sign operation. Leaving pss_salt unset keeps today's internally-generated-salt behavior unchanged. Signed-off-by: Sucharitha Sarananaga <[email protected]> ---
Acked-by: Radu Nicolau <[email protected]>
