[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20091212192712.GB1308@ucw.cz>
Date: Sat, 12 Dec 2009 20:27:12 +0100
From: Pavel Machek <pavel@....cz>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Ferenc Wagner <wferi@...f.hu>, linux-pm@...ts.linux-foundation.org,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, netdev@...r.kernel.org
Subject: s2disk encryption was Re: [linux-pm] intermittent suspend problem
again
Hi!
> > >> On the other hand, I reverted 8fbd962e3, recompiled and replaced the
> > >> module, and got the freeze during hibernation. And that was the bulk of
> > >> the changes since 2.6.31... I'll revert the rest and test again, but
> > >> that seems purely cosmetic, so no high hopes.
> > >>
> > >>> In addition to that, you can run multiple hibernation/resume cycles in
> > >>> a tight loop using the RTC wakealarm.
> > >>
> > >> I'll do so, as soon as I find a way to automatically supply the dm-crypt
> > >> passphrase... or even better, learn to hibernate to ramdisk from the
> > >> initramfs. :)
> > >
> > > Well, you don't need to use swap encryption for _testing_. :-)
> >
> > I use partition encryption, everything except for /boot is encrypted.
>
> If /boot is big enough, you could use a swap file in /boot for the testing.
>
> > Apropos: does s2disk perform encryption with a temporary key even if I
> > don't supply and RSA key, to protect mlocked application data from being
> > present in the swap after restore?
>
> It can do that, but you need to provide a key during suspend and resume.
>
> Otherwise it doesn't use a random key, because it would have to store it in
> the clear in the image header.
I believe it can use random key, stored in clear in image
header. Reason is... image header is easier to overwrite than removing
whole image.
That was original motivation for encryption... not having to overwrite
swap data with zeros.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists