[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20180626111245.GA25323@amd>
Date: Tue, 26 Jun 2018 13:12:45 +0200
From: Pavel Machek <pavel@....cz>
To: Oliver Neukum <oneukum@...e.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Chen Yu <yu.c.chen@...el.com>, Ted Ts'o <tytso@....edu>,
Len Brown <len.brown@...el.com>,
"Lee, Chun-Yi" <jlee@...e.com>, Borislav Petkov <bp@...en8.de>,
Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J . Wysocki" <rafael.j.wysocki@...el.com>,
Stephan Mueller <smueller@...onox.de>,
Eric Biggers <ebiggers3@...il.com>,
Denis Kenzior <denkenz@...il.com>
Subject: Re: [PATCH 3/3][RFC] tools: create power/crypto utility
On Tue 2018-06-26 12:30:24, Oliver Neukum wrote:
> On Di, 2018-06-26 at 00:16 +0200, Pavel Machek wrote:
> > Interested parties can easily fix up the userland parts of uswsusp,
> >
> > change crypto, add or remove dependencies, move it to other hosting,
> >
> > or drop it and start again. Kernel interface is flexible enough. If
> >
> > Chen wants to move the s2disk encryption into kernel, it is his task
> >
> > to explain why that is neccessary.
>
> We would have to assume that the kernel is on a higher level of trust.
> To a certain extent it is.You cannot drop support for /dev/kmem conceptionally
> if there is an ioctl to snapshot it.
If I understood the description, proposed patches give userspace encryption
key + image encrypted with that key. So... that's not really an
improvement.
Anyway, I guess it makes sense to wait for v2 of patches with better
description of security goals of this.
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