[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4499700.LRS4F2YjjC@tauon.chronox.de>
Date: Mon, 07 Jan 2019 16:52:00 +0100
From: Stephan Mueller <smueller@...onox.de>
To: herbert@...dor.apana.org.au
Cc: "Lee, Chun-Yi" <joeyli.kernel@...il.com>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, keyrings@...r.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Chen Yu <yu.c.chen@...el.com>,
Oliver Neukum <oneukum@...e.com>,
Ryan Chen <yu.chen.surf@...il.com>,
David Howells <dhowells@...hat.com>,
Giovanni Gherdovich <ggherdovich@...e.cz>,
Randy Dunlap <rdunlap@...radead.org>,
Jann Horn <jannh@...gle.com>, Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH 1/5 v2] PM / hibernate: Create snapshot keys handler
Am Montag, 7. Januar 2019, 16:33:27 CET schrieb joeyli:
Hi Herbert,
>
> > use an official KDF type like SP800-108 or HKDF?
> >
> > You find the counter-KDF according to SP800-108 in security/keys/dh.c
> > (search for functions *kdf*).
> >
> > Or we may start pulling in KDF support into the kernel crypto API via the
> > patches along the line of [1].
> >
> > [1] http://www.chronox.de/kdf.html
>
> Thanks for your suggestion. I didn't touch any key derivation standard
> before. I will study it.
>
> But I still want to use my original function currently. Because the same
> logic is also used in trusted key. I will happy to move to SP800-108 or
> HKDF when it's available in kernel.
Would it make sense to polish these mentioned KDF patches and add them to the
kernel crypto API? The sprawl of key derivation logic here and there which
seemingly does not comply to any standard and thus possibly have issues should
be prevented and cleaned up.
Ciao
Stephan
Powered by blists - more mailing lists