[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190107180703.GE933@amd>
Date: Mon, 7 Jan 2019 19:07:03 +0100
From: Pavel Machek <pavel@....cz>
To: joeyli <jlee@...e.com>
Cc: "Lee, Chun-Yi" <joeyli.kernel@...il.com>,
"Rafael J . Wysocki" <rjw@...ysocki.net>,
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 0/5 v2][RFC] Encryption and authentication for hibernate
snapshot image
Hi!
> Thanks for your review!
>
> > > The hibernate function can be used to snapshot memory pages to an image,
> > > then kernel restores the image to memory space in a appropriate time.
> > > There have secrets in snapshot image and cracker may modifies it for
> > > hacking system. Encryption and authentication of snapshot image can protect
> > > the system.
> > >
> > > Hibernate function requests the master key through key retention service.
> > > The snapshot master key can be a trusted key or a user defined key. The
> > > name of snapshot master key is fixed to "swsusp-kmk". User should loads
> > > swsusp-kmk to kernel by keyctl tool before the hibernation resume.
> > > e.g. The swsusp-kmk must be loaded before systemd-hibernate-resume
> >
> > But if userspace has a key, encryption is useless against root.
> >
>
> Yes, but this concern is not only for hibernation encryption. This patch
> set does not provide solution against this concern.
So, can we postpone these patches until we have a solution secure
against root users?
> My security goals:
>
> - Encrypt and authicate hibernate snapshot image in kernel space. Userspace
> can only touch an encrypted and signed snapshot image.
>
> - The code of encryption are in kernel. They will be signed and verify with
> kernel binary when secure boot enabled. It's better than using
> unauthenticated userspace code at runtime.
These are not goals. I'd like to understand why you want to put it into
kernel in the first place.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists