lkml.org 
[lkml]   [2019]   [Jan]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [RFC PATCH 4/5] crypto: Adds user space interface for ALG_SET_KEY_TYPE
Date
Am Donnerstag, 17. Januar 2019, 08:02:20 CET schrieb Kalyani Akula:

Hi Kalyani,

> ALG_SET_KEY_TYPE requires caller to pass the key_type to be used
> for AES encryption/decryption.
>
> Sometimes the cipher key will be stored in the
> device's hardware. So, there is a need to specify
> the information about the key to use for AES operations.
>
> In Xilinx ZynqMP SoC, below key types are available
>
> 1. Device key, which is flashed in the HW.
>
> 2. PUF KEK, which can be regenerated using the
> helper data programmed in the HW.
>
> 3. User supplied key.
>
> So to choose the AES key to be used, this patch adds key-type attribute.

You expose your particular driver interface to user space. So, user space
would need the details of you driver to know what to set. If another driver
has such key type support, user space would need to know about that, too. I do
not think this is a wise idea.

If we are going to have such a keytype selection, there must be a common user
space interface for all drivers. I.e. define common key types the drivers then
can map to their particular key type interface.

Besides, seem to be more a key handling issue. Wouldn't it make sense to
rather have such issue solved with key rings than in the kernel crypto API?

Ciao
Stephan


\
 
 \ /
  Last update: 2019-01-17 12:35    [W:0.095 / U:5.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site