Am Mittwoch, 19. April 2017, 14:03:35 CEST schrieb Tudor Ambarus: Hi Tudor, > Hi, Stephan, Herbert, > > On 19.04.2017 02:03, Stephan Müller wrote: > > The patch 8 describes the different operations that are supported by > > AF_ALG > > KPP. This support includes generation and retaining of the private key > > inside the kernel. This private key would never be sent to user space. > > There are crypto co-processors that are capable of generating and > retaining the private key inside the device without revealing it to > kernel. The private key will be further used to generate the public > key and the shared secret. Should we extend the KPP API to support this? The less software has access to secrets, the better. Thus, having such API would be good. This of course assumes that the private key is generated with an appropriate RNG. As normal users cannot verify the RNG or the noise sources implemented in hardware, the choice of using such API to keep the private key inside the hardware should be left to the caller. >From the AF_ALG KPP support side, I could imagine that that the algif_kpp code makes use of the hardware support unless the caller objects. Ciao Stephan
