On Thu, Aug 05, 2010 at 10:17:53PM +0200, Miloslav Trmač wrote: > Hello, > following is a patchset providing an user-space interface to the kernel crypto > API. It is based on the older, BSD-compatible, implementation, but the > user-space interface is different. > > These are the major differences compared to the BSD-like interface: > > * The API supports key storage and management inside the kernel. > An application can thus ask the kernel to generate a key; the key is > then referenced via an integer identifier, and the application can be > prevented from accessing the raw key data. Such a key can, if so configured, > still be wrapped for key transport to the recipient of the message, and > unwrapped by the recipient. > > The kernel key storage does not span system reboots, but applications can > also wrap the keys for persistent storage, receiving an encrypted blob that > does not reveal the raw key data, but can be later loaded back into the > kernel. > > * More algorithms and mechanisms are supported by the API, including public key > algorithms (RSA/DSA encryption and signing, D-H key derivation, key wrapping). Thanks for the patches. Unfortunately it fails to satisfy the requirement of supporting all our existing kernel crypto interfaces, such as AEAD, as well as being flexible enough in adding new interfaces such as xor. So we need to address these issues before this can be integrated into Linux. Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
