public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alon Bar-Lev <alon.barlev@gmail.com>
To: Pavel Machek <pavel@suse.cz>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Peter Wainwright <prw@ceiriog.eclipse.co.uk>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Announcing crypto suspend
Date: Tue, 21 Mar 2006 00:05:27 +0200	[thread overview]
Message-ID: <441F2727.6020407@gmail.com> (raw)
In-Reply-To: <20060320213400.GI24523@elf.ucw.cz>

Pavel Machek wrote:
 > 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.

Pavel, you keep doing the same basic mistake...
Understand your client!

Suspend is a feature that is most used by the mobile community.
Disk encryption is also common for most of this community.
Putting them to work together should be your interest...
Calling your clients stupid is not wise!

> 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].

Well... Good thinking... But how do you plan to encrypt the
swap? There are about 1000 ways to do this...

Jari Ruusu had written the loop-aes which was not merged...
>From a similar reason suspend2 was rejected by you.

I hope you don't think that file-system encryption should be
implemented in user mode too...

The dm-crypt is weak... So we left with specific encryption
implementation of swsusp... And now you offer a specific
encryption for swap as well... Why not realize that there
should be one encryption solution for block devices in kernel?

As a result of this mess the mobile community uses external
solutions.

Best Regards,
Alon Bar-Lev.

  reply	other threads:[~2006-03-20 22:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20  8:04 Announcing crypto suspend 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
2006-03-20 22:05               ` Alon Bar-Lev [this message]
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=441F2727.6020407@gmail.com \
    --to=alon.barlev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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