Re: [PATCH v3 03/19] crypto: cmh - add key provisioning and management
Krzysztof Kozlowski <[email protected]>
| Newsgroups | org.kernel.vger.linux-api,org.infradead.lists.linux-riscv,org.kernel.vger.linux-crypto,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-doc,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest |
|---|---|
| Message-ID | <20260811-belligerent-analytic-sheep-3fce16@quoll> |
On Thu, Aug 06, 2026 at 12:55:02PM -0700, Saravanakrishnan Krishnamoorthy wrote: > From: Alex Ousherovitch <[email protected]> > > Add the CMH key management subsystem: > > - Key provisioning: create, import, derive, and destroy hardware keys > stored in the CMH datastore > - System object management: allocate and free CMH system objects > - Management ioctl interface (/dev/cmh_mgmt): ioctl commands > covering key lifecycle, KIC key derivation, PKE operations (RSA, > ECDSA, ECDH, EdDSA), PQC operations (ML-KEM, ML-DSA, SLH-DSA), > SM2, EAC, and DRBG reseeding > - SM2 ioctl handlers: SM2 encrypt, decrypt, sign, and key exchange > -- operations that require multi-step protocol flows not > expressible through the standard crypto API sig interface > - UAPI header: cmh_mgmt_ioctl.h (ioctl definitions and structures) And we need custom IOCTL interface because existing kernel interfaces are ... ? Say something useful in commit msg, e.g. WHY you are doing this, not what you are doing. Best regards, Krzysztof