From: Pavel Machek <pavel@ucw.cz>
To: Evan Green <evgreen@chromium.org>
Cc: linux-kernel@vger.kernel.org,
Matthew Garrett <mgarrett@aurora.tech>,
dlunev@google.com, zohar@linux.ibm.com, jejb@linux.ibm.com,
linux-integrity@vger.kernel.org, corbet@lwn.net,
rjw@rjwysocki.net, gwendal@chromium.org, jarkko@kernel.org,
linux-pm@vger.kernel.org, David Howells <dhowells@redhat.com>,
Hao Wu <hao.wu@rubrik.com>, James Morris <jmorris@namei.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Len Brown <len.brown@intel.com>,
Matthew Garrett <matthewgarrett@google.com>,
Peter Huewe <peterhuewe@gmx.de>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Serge E. Hallyn" <serge@hallyn.com>, axelj <axelj@axis.com>,
keyrings@vger.kernel.org, linux-doc@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH 00/10] Encrypted Hibernation
Date: Fri, 6 May 2022 18:08:08 +0200 [thread overview]
Message-ID: <20220506160807.GA1060@bug> (raw)
In-Reply-To: <20220504232102.469959-1-evgreen@chromium.org>
Hi!
> We are exploring enabling hibernation in some new scenarios. However,
> our security team has a few requirements, listed below:
> 1. The hibernate image must be encrypted with protection derived from
> both the platform (eg TPM) and user authentication data (eg
> password).
> 2. Hibernation must not be a vector by which a malicious userspace can
> escalate to the kernel.
Can you (or your security team) explain why requirement 2. is needed?
On normal systems, trusted userspace handles kernel upgrades (for example),
so it can escalate to kernel priviledges.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2022-05-06 16:09 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 23:20 [PATCH 00/10] Encrypted Hibernation Evan Green
2022-05-04 23:20 ` [PATCH 01/10] tpm: Add support for in-kernel resetting of PCRs Evan Green
2022-05-04 23:20 ` [PATCH 02/10] tpm: Allow PCR 23 to be restricted to kernel-only use Evan Green
2022-05-04 23:20 ` [PATCH 03/10] security: keys: trusted: Parse out individual components of the key blob Evan Green
2022-05-04 23:20 ` [PATCH 04/10] security: keys: trusted: Allow storage of PCR values in creation data Evan Green
2022-08-02 23:00 ` Eric Biggers
2022-08-03 20:48 ` Evan Green
2022-05-04 23:20 ` [PATCH 05/10] security: keys: trusted: Verify " Evan Green
2022-05-04 23:20 ` [PATCH 06/10] PM: hibernate: Add kernel-based encryption Evan Green
2022-08-29 21:45 ` TPM: hibernate with IMA PCR 10 Ken Goldman
2022-08-29 21:51 ` Matthew Garrett
2022-08-31 2:48 ` Jarkko Sakkinen
2022-09-07 20:47 ` Evan Green
2022-09-07 23:57 ` Mimi Zohar
2022-09-08 5:25 ` Jarkko Sakkinen
2022-09-11 2:40 ` Mimi Zohar
2022-09-20 4:36 ` Jarkko Sakkinen
2022-09-21 20:15 ` Mimi Zohar
2022-09-23 13:30 ` Jarkko Sakkinen
2022-09-27 16:03 ` Evan Green
2022-09-28 9:42 ` Jonathan McDowell
2022-05-04 23:20 ` [PATCH 07/10] PM: hibernate: Use TPM-backed keys to encrypt image Evan Green
2022-05-04 23:21 ` [PATCH 08/10] PM: hibernate: Mix user key in encrypted hibernate Evan Green
2022-05-06 16:08 ` Pavel Machek
2022-05-09 16:44 ` Evan Green
2022-05-10 12:29 ` Pavel Machek
2022-05-10 16:02 ` Evan Green
2022-08-02 22:48 ` Eric Biggers
2022-08-03 20:48 ` Evan Green
2022-05-04 23:21 ` [PATCH 09/10] PM: hibernate: Verify the digest encryption key Evan Green
2022-08-02 22:51 ` Eric Biggers
2022-05-04 23:21 ` [PATCH 10/10] PM: hibernate: seal the encryption key with a PCR policy Evan Green
2022-05-06 16:08 ` Pavel Machek [this message]
2022-05-09 16:43 ` [PATCH 00/10] Encrypted Hibernation Evan Green
2022-05-17 16:06 ` Rafael J. Wysocki
2022-05-17 17:34 ` Evan Green
2022-06-16 15:42 ` Evan Green
2022-08-01 22:32 ` Evan Green
2022-08-02 18:36 ` Matthew Garrett
2022-08-04 0:59 ` Jarkko Sakkinen
2022-08-04 21:55 ` Evan Green
2022-08-06 18:21 ` Jarkko Sakkinen
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=20220506160807.GA1060@bug \
--to=pavel@ucw.cz \
--cc=axelj@axis.com \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=dlunev@google.com \
--cc=evgreen@chromium.org \
--cc=gwendal@chromium.org \
--cc=hao.wu@rubrik.com \
--cc=jarkko@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=mgarrett@aurora.tech \
--cc=peterhuewe@gmx.de \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).