From: joeyli <jlee@suse.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Chen Yu <yu.c.chen@intel.com>, Oliver Neukum <oneukum@suse.com>,
Ryan Chen <yu.chen.surf@gmail.com>,
David Howells <dhowells@redhat.com>,
Giovanni Gherdovich <ggherdovich@suse.cz>
Subject: Re: [PATCH 1/5] PM / hibernate: Create snapshot keys handler
Date: Thu, 13 Sep 2018 16:39:16 +0800 [thread overview]
Message-ID: <20180913083916.GE3593@linux-l9pv.suse> (raw)
In-Reply-To: <b3dd8655-c394-ed62-1efc-8295a95bb7fb@infradead.org>
Hi Randy,
On Wed, Sep 12, 2018 at 09:27:27AM -0700, Randy Dunlap wrote:
> Hi,
>
> On 9/12/18 7:23 AM, Lee, Chun-Yi wrote:
> > diff --git a/kernel/power/Kconfig b/kernel/power/Kconfig
> > index 3a6c2f87699e..7c5c30149dbc 100644
> > --- a/kernel/power/Kconfig
> > +++ b/kernel/power/Kconfig
> > @@ -76,6 +76,20 @@ config HIBERNATION
> >
> > For more information take a look at <file:Documentation/power/swsusp.txt>.
> >
> > +config HIBERNATION_ENC_AUTH
> > + bool "Hibernation encryption and authentication"
> > + depends on HIBERNATION
> > + depends on TRUSTED_KEYS
> > + select CRYPTO_AES
> > + select CRYPTO_HMAC
> > + select CRYPTO_SHA512
> > + help
> > + This option will encrypt and authenticate the memory snapshot image
> > + of hibernation. It prevents that the snapshot image be arbitrary
>
> arbitrarily
>
> > + modified. User can use TPMs trusted key or user defined key as the
>
> The user
> or A user can use the TPM's trusted key
>
Thanks for your review! I will update it in next version.
Joey Lee
next prev parent reply other threads:[~2018-09-13 8:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 14:23 [PATCH 0/5][RFC] Encryption and authentication for hibernate snapshot image Lee, Chun-Yi
2018-09-12 14:23 ` [PATCH 1/5] PM / hibernate: Create snapshot keys handler Lee, Chun-Yi
2018-09-12 16:27 ` Randy Dunlap
2018-09-13 8:39 ` joeyli [this message]
2018-09-13 13:58 ` Yu Chen
2018-10-01 10:47 ` joeyli
2018-09-13 14:31 ` Jann Horn
2018-09-13 14:31 ` Jann Horn
2018-10-02 7:54 ` joeyli
2018-10-02 7:54 ` joeyli
2018-10-02 19:36 ` Jann Horn
2018-10-02 19:36 ` Jann Horn
2018-10-03 22:08 ` Andy Lutomirski
2018-10-03 22:08 ` Andy Lutomirski
2018-10-08 13:29 ` joeyli
2018-10-08 13:29 ` joeyli
2018-10-08 13:29 ` joeyli
2018-10-04 4:02 ` Mimi Zohar
2018-10-04 4:02 ` Mimi Zohar
2018-09-14 5:52 ` kbuild test robot
2018-09-12 14:23 ` [PATCH 2/5] PM / hibernate: Generate and verify signature for snapshot image Lee, Chun-Yi
2018-09-12 14:23 ` [PATCH 3/5] PM / hibernate: Encrypt " Lee, Chun-Yi
2018-09-12 14:23 ` [PATCH 4/5] PM / hibernate: Erase the snapshot master key in snapshot pages Lee, Chun-Yi
2018-09-12 14:23 ` [PATCH 5/5] PM / hibernate: An option to request that snapshot image must be authenticated Lee, Chun-Yi
2018-09-12 16:24 ` Randy Dunlap
2018-09-13 8:37 ` joeyli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180913083916.GE3593@linux-l9pv.suse \
--to=jlee@suse.com \
--cc=dhowells@redhat.com \
--cc=ggherdovich@suse.cz \
--cc=joeyli.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=pavel@ucw.cz \
--cc=rafael.j.wysocki@intel.com \
--cc=rdunlap@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=yu.c.chen@intel.com \
--cc=yu.chen.surf@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.