From: Brandon Low <lostlogic@gentoo.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-mm1
Date: Wed, 18 Feb 2004 14:52:06 -0600 [thread overview]
Message-ID: <20040218205206.GD449@lostlogicx.com> (raw)
In-Reply-To: <20040218125227.0bf7dc2f.akpm@osdl.org>
On Wed, 02/18/04 at 12:52:27 -0800, Andrew Morton wrote:
> Brandon Low <lostlogic@gentoo.org> wrote:
> >
> > but if people are depending on that support to stay
> > in a stable kernel and are developing based on it and don't have the
> > time to learn dm or dmcrypto and redesign whatever may need redesigning
> > to use it, it strikes me as rude to pull that support.
>
> This is actually an argument for removing cryptolooop. People are
> developing against a crypto infrastructure which has well-known weaknesses.
>
> Pulling it out is an excellent way of communicating this fact. Right now,
> we're just deluding people.
Unfortunately, you have a valid point... I don't like it, because it
means work for me, but it is a valid point...
I am just reading up on dm now, but correct me if I am wrong, I will
need to do losetup, dmcreate, mount in that order in order to use
dmcrypt on loop where with cryptoloop, I could just do "mount"... there
must be an easier way to handle this!
Thanks,
Brandon
next prev parent reply other threads:[~2004-02-18 20:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 7:21 2.6.3-mm1 Andrew Morton
2004-02-18 7:43 ` 2.6.3-mm1 Andrew Morton
2004-02-18 9:25 ` 2.6.3-mm1 Andrew Morton
2004-02-18 13:42 ` 2.6.3-mm1 Rusty Russell
2004-02-18 18:50 ` 2.6.3-mm1 Andrew Morton
2004-02-18 11:13 ` 2.6.3-mm1 Sean Neakums
2004-02-18 11:14 ` 2.6.3-mm1 Jonathan Brown
2004-02-18 12:37 ` 2.6.3-mm1 Sean Neakums
2004-02-18 12:14 ` dmcrypt works well on 2.6.3 WAS: 2.6.3-mm1 bert hubert
2004-02-18 14:26 ` 2.6.3-mm1 Ramon Rey Vicente
2004-02-18 18:55 ` 2.6.3-mm1 Andrew Morton
2004-02-18 19:06 ` 2.6.3-mm1 Matthew Wilcox
2004-02-18 16:16 ` 2.6.3-mm1 Bill Davidsen
2004-02-18 20:04 ` 2.6.3-mm1 Brandon Low
2004-02-18 20:22 ` 2.6.3-mm1 Andrew Morton
2004-02-18 20:33 ` 2.6.3-mm1 Brandon Low
2004-02-18 20:52 ` 2.6.3-mm1 Andrew Morton
2004-02-18 20:52 ` Brandon Low [this message]
2004-02-18 21:00 ` 2.6.3-mm1 Andrew Morton
2004-02-18 22:15 ` 2.6.3-mm1 Christophe Saout
2004-02-19 0:33 ` 2.6.3-mm1 Brandon Low
2004-02-19 12:39 ` 2.6.3-mm1 Christophe Saout
2004-02-18 17:50 ` 2.6.3-mm1 James Simmons
2004-02-22 2:46 ` 2.6.3-mm1 William Lee Irwin III
[not found] <20040217232130.61667965.akpm@osdl.org.suse.lists.linux.kernel>
2004-02-18 10:43 ` 2.6.3-mm1 Andi Kleen
2004-02-18 10:55 ` 2.6.3-mm1 Andrew Morton
2004-02-19 6:37 ` 2.6.3-mm1 Andi Kleen
2004-02-18 13:45 ` 2.6.3-mm1 Joe Thornber
2004-02-19 11:52 ` 2.6.3-mm1 Andi Kleen
2004-02-18 23:27 ` 2.6.3-mm1 Andrew Morton
2004-02-19 17:54 ` 2.6.3-mm1 Andi Kleen
[not found] <1qujU-5xX-31@gated-at.bofh.it>
[not found] ` <1qCUf-4vn-41@gated-at.bofh.it>
[not found] ` <1qGuR-bb-25@gated-at.bofh.it>
[not found] ` <1qGO2-uG-13@gated-at.bofh.it>
[not found] ` <1qGO5-uG-21@gated-at.bofh.it>
[not found] ` <1qGY1-RT-29@gated-at.bofh.it>
[not found] ` <1qGY1-RT-27@gated-at.bofh.it>
[not found] ` <1qIn3-5yq-23@gated-at.bofh.it>
2004-02-19 21:58 ` 2.6.3-mm1 Bill Davidsen
2004-02-19 22:01 ` 2.6.3-mm1 Christophe Saout
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=20040218205206.GD449@lostlogicx.com \
--to=lostlogic@gentoo.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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