From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alon Bar-Lev <alon.barlev@gmail.com>,
Peter Wainwright <prw@ceiriog.eclipse.co.uk>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Announcing crypto suspend
Date: Mon, 20 Mar 2006 22:34:00 +0100 [thread overview]
Message-ID: <20060320213400.GI24523@elf.ucw.cz> (raw)
In-Reply-To: <200603202222.14634.rjw@sisk.pl>
On Po 20-03-06 22:22:13, Rafael J. Wysocki wrote:
> On Monday 20 March 2006 21:35, Pavel Machek wrote:
> > On Po 20-03-06 21:26:23, Rafael J. Wysocki wrote:
> > > On Monday 20 March 2006 20:11, Alon Bar-Lev wrote:
> > > > Rafael J. Wysocki wrote:
> > > > > and please read the HOWTO. Unfortunately the RSA-related part hasn't been
> > > > > documented yet, but it's pretty straightforward.
> > > >
> > > > Hello,
> > > >
> > > > I don't understand why you are working so hard on this... If
> > > > you want encryption, you should care about all of your data!
> > >
> > > I hope you realize there may be sensitive data in the suspend image
> > > that are not stored in filesystems (eg. crypto keys, passwords etc.).
> >
> > If you have your swap partition on encrypted filesystem, that may
> > actually work okay.
>
> Yes, but that's why you may want to encrypt suspend images even if you
> don't need to encrypt your filesystems. :-)
Of course, agreed. Encrypting filesystem is stupid thing from
data-recovery standpoint; and I care about my data; it is also hard to
backup. For some uses it is of course neccessary, but it has lots of
disadvantages, too.
Encrypted swsusp has basically no disadvantages.
[I believe we should encrypt swap with random key generated on boot by
default. That should be also very cheap, and has no real
disadvantages].
Pavel
--
Picture of sleeping (Linux) penguin wanted...
next prev parent reply other threads:[~2006-03-20 21:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 8:04 Pavel Machek
2006-03-20 14:13 ` Andreas Jellinghaus
2006-03-20 18:35 ` Peter Wainwright
2006-03-20 18:44 ` Pavel Machek
2006-03-20 19:26 ` Peter Wainwright
2006-03-20 18:54 ` Rafael J. Wysocki
2006-03-20 19:11 ` Alon Bar-Lev
2006-03-20 20:26 ` Rafael J. Wysocki
2006-03-20 20:35 ` Pavel Machek
2006-03-20 21:22 ` Rafael J. Wysocki
2006-03-20 21:34 ` Pavel Machek [this message]
2006-03-20 22:05 ` Alon Bar-Lev
2006-03-20 22:18 ` Pavel Machek
2006-03-20 22:24 ` Andreas Happe
2006-03-21 9:45 ` Andreas Jellinghaus
2006-03-21 20:50 ` Pavel Machek
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=20060320213400.GI24523@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=alon.barlev@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prw@ceiriog.eclipse.co.uk \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®