From: Matt Mackall <mpm@selenic.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Alexander Nyberg <alexn@dsv.su.se>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: dm-crypt vs. cryptoloop reminder
Date: Thu, 10 Mar 2005 13:02:18 -0800 [thread overview]
Message-ID: <20050310210218.GB3163@waste.org> (raw)
In-Reply-To: <20050309193212.GB632@openzaurus.ucw.cz>
On Wed, Mar 09, 2005 at 08:32:13PM +0100, Pavel Machek wrote:
> Hi!
>
> > > 2.6.3-mm1 'dm-crypt vs. cryptoloop' discussion was some time ago, it is
> > > time to bring this up again:
> > > http://kerneltrap.org/node/2433
> >
> > Are you a troll?
> >
> > This is not something to be quoted by anybody serious.
> >
> > Andrew referred to "well-known weaknesses" in cryptoloop,
> > and when I inquired it turned out that what he referred to
> > were properties of cryptoloop and dm-crypt alike, so that
> > his remarks that started that discussion were misguided.
> >
> > Of course people may prefer dm-crypt or cryptoloop or loop-aes,
> > just like people prefer ide-cd or ide-scsi.
> >
> > I have not yet seen a valid reason to deprecate one of these three
> > very soon.
>
> I'd say that "no-maintainer" + "maintained code can do the same" is enough, but...
> I thought that ide-scsi was deprecated, too?
You can attach a file to loopback and then run dm-crypt on top of
that, so I think it's completely duplicate functionality at this
point.
--
Mathematics is the supreme nostalgia of our time.
prev parent reply other threads:[~2005-03-10 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 21:35 dm-crypt vs. cryptoloop reminder Alexander Nyberg
2005-03-05 22:44 ` Andries Brouwer
2005-03-09 19:32 ` Pavel Machek
2005-03-10 21:02 ` Matt Mackall [this message]
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=20050310210218.GB3163@waste.org \
--to=mpm@selenic.com \
--cc=aebr@win.tue.nl \
--cc=akpm@osdl.org \
--cc=alexn@dsv.su.se \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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