mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jeremy Maitin-Shepard <jeremy@jeremyms.com>
Cc: Nigel Cunningham <ncunningham@crca.org.au>,
	tuxonice-devel@lists.tuxonice.net, linux-kernel@vger.kernel.org,
	Rafael Wysocki <rjw@sisk.pl>
Subject: Re: [TuxOnIce-devel] RFC: Suspend-to-ram cold boot protection by encrypting page cache
Date: Sun, 12 Jul 2009 00:10:39 +0200	[thread overview]
Message-ID: <20090711221039.GC1670@ucw.cz> (raw)
In-Reply-To: <87hbxl587g.fsf@jeremyms.com>

On Fri 2009-07-10 00:05:23, Jeremy Maitin-Shepard wrote:
> Pavel Machek <pavel@ucw.cz> writes:
> 
> > On Wed 2009-07-08 04:09:41, Jeremy Maitin-Shepard wrote:
> >> Pavel Machek <pavel@ucw.cz> writes:
> >> 
> >> > On Wed 2009-07-08 03:47:53, Jeremy Maitin-Shepard wrote:
> >> >> Pavel Machek <pavel@ucw.cz> writes:
> >> >> 
> >> >> [snip]
> >> >> 
> >> >> > I believe uswsusp could be used rather easily. Just modify s2disk to
> >> >> > encrypt image in ram without writing it out, then decrypt it from ram
> >> >> > and resume... it should be interesting hack.
> >> >> 
> >> >> As far as I understand, that would be completely useless since the image
> >> >> that would be encrypted would just be a copy of what would still remain
> >> >> in memory.
> >> 
> >> > Yes... so next step would be kernel call that would erase all the
> >> > pagecache and anonymous pages. You would still leave some data in
> >> > kernel structures, but that would be quite hard to fix. 
> >> 
> >> Okay.  (This does still require the same assumption as TuxOnIce
> >> regarding the page cache, though.)
> 
> > (Not sure; clearing the page cache could be done atomically, from
> > interrupts disabled. But I'm no mm expert.)
> 
> But surely it wouldn't work to leave interrupts disabled after that
> until the page cache is restored.  After the page cache (and other
> sensitive memory) is encrypted, after possibly entering and resuming
> from S3, the page cache needs to be decrypted.  Userspace will be
> doing

I see no need for that. You'd do something like 'kill -9 -1; echo 3 >
drop_caches' after snapshot, then scrub free ram. At that point you
should have no sensitive data in the memory, and encrypted image you
can restore.

(Now, kill -9 -1 with frozen tasks may be tricky to implement....)
									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-07-12 11:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01  6:07 Jeremy Maitin-Shepard
2009-07-01  6:24 ` [TuxOnIce-devel] " Nigel Cunningham
2009-07-01  6:43   ` Jeremy Maitin-Shepard
2009-07-01  9:09     ` Nigel Cunningham
2009-07-01 15:55       ` Rafael J. Wysocki
2009-07-01 20:57         ` Jeremy Maitin-Shepard
2009-07-01 22:41           ` Rafael J. Wysocki
2009-07-01 22:58             ` Nigel Cunningham
2009-07-01 23:06             ` Jeremy Maitin-Shepard
2009-07-02  5:14               ` U Kuehn
2009-07-02  5:47                 ` Jeremy Maitin-Shepard
2009-07-02 16:12               ` Rafael J. Wysocki
2009-07-04  2:44       ` Pavel Machek
2009-07-08 10:47         ` Jeremy Maitin-Shepard
2009-07-04  2:57           ` Pavel Machek
2009-07-08 11:09             ` Jeremy Maitin-Shepard
2009-07-09 10:14               ` Pavel Machek
2009-07-10  7:05                 ` Jeremy Maitin-Shepard
2009-07-11 22:10                   ` Pavel Machek [this message]
2009-07-01 12:21 ` Jens Gustedt
2009-07-01 20:40   ` Jeremy Maitin-Shepard

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=20090711221039.GC1670@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=jeremy@jeremyms.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@crca.org.au \
    --cc=rjw@sisk.pl \
    --cc=tuxonice-devel@lists.tuxonice.net \
    /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

Powered by JetHome