lkml.org 
[lkml]   [2021]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Migration to trusted keys: sealing user-provided key?
From
Date
On Mon, 2021-02-08 at 16:50 -0500, Mimi Zohar wrote:
> On Mon, 2021-02-08 at 15:38 +0100, Jan Lübbe wrote:
>
> > As it seems that this feature would not be appropriate for all use-cases and
> > threat models, I wonder if making it optional would be acceptable. Something
> > like:
> >
> > config TRUSTED_KEYS_IMPORT
>
> To me "IMPORT" implies from a trusted source, which this is not.
> Perhaps "UNSAFE_IMPORT", "DEBUGGING_IMPORT, "DEVELOPMENT_IMPORT", ...
>
> Defining a Kconfig with any of these names and the other changes below,
> makes it very clear using predefined key data is not recommended. My
> concern with extending trusted keys to new trust sources is the
> implication that the security/integrity is equivalent to the existing
> discrete TPM.
>
> >         bool "Allow creating TRUSTED KEYS from existing key material"
> >         depends on TRUSTED_KEYS
>
> Missing "default n"

According to Documentation/kbuild/kconfig-language.rst: "The default value
deliberately defaults to 'n' in order to avoid bloating the build.". So an
explicit "default n" should not be needed. I'll add it though, for now.

> >         help
> >           This option adds support for creating new trusted keys from
> > existing
> >           key material supplied by userspace, instead of using random
> > numbers.
> >           As with random trusted keys, userspace cannot extract the plain-
> > text
>
> Once defined, as with random trusted keys, userspace cannot ...
>
> >           key material again and will only ever see encrypted blobs.
> >           
> >
> >           This option should *only* be enabled for use in a trusted
> >           environment (such as during debugging/development or in a secured
> >           factory). Also, consider using 'keyctl padd' instead of 'keyctl
> > add'
>
> Even the "secured factory" is not a good idea. Please limit the usage
> to debugging/development.
>
> >           to avoid exposing the plain-text key on the process command line.
> >
> >           If you are unsure as to whether this is required, answer N.
>
> The above would be fine.

OK, that would result in:

config TRUSTED_KEYS_DEVELOPMENT_IMPORT
        bool "Allow creating TRUSTED KEYS from existing key material for development"
        depends on TRUSTED_KEYS
default n
        help
          This option adds support for creating new trusted keys from
existing key material supplied by userspace, instead of using
random numbers. Once defined,  as with random trusted keys,
userspace cannot extract the plain-text key material again
and will only ever see encrypted blobs.
          
          This option should *only* be enabled for debugging/development.
Also, consider using 'keyctl padd' instead of 'keyctl add' to
avoid exposing the plain-text key on the process command line.

          If you are unsure as to whether this is required, answer N.

Thanks,
Jan
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |

\
 
 \ /
  Last update: 2021-02-09 08:18    [W:0.090 / U:1.428 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site