mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Gilbert <michael.s.gilbert@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: CVE-2004-2135 and CVE-2004-2136
Date: Thu, 3 Dec 2009 20:53:11 -0500	[thread overview]
Message-ID: <20091203205311.9a9478e4.michael.s.gilbert@gmail.com> (raw)
In-Reply-To: <20091203165321.GB6416@tatooine.rebelbase.local>

On Thu, 3 Dec 2009 17:53:21 +0100 markus reichelt wrote:
> * Michael Gilbert wrote:
> 
> > CVE-2004-2135 [0] and CVE-2004-2136 [1] were disclosed over five
> > years ago; however, i have been unable to verify whether they have
> > been fixed or not in the latest kernels.
> 
> They are not, and both CVE-entries are still marked as 'candidate'.
> Add the fact that (crypto)loop code has had a poor relation with the
> vanilla kernel in favour of dm-crypt, and is also unmaintained,
> nobody really cares.
> 
> Did you receive any other replies to your mail? Just curious.

None so far.  Would it make sense to remove cryptoloop at this point
since it obviously has some major design/implementation weaknesses?
Apropos, there are two other full-disk encryption options (dm-crypt and
loop-aes) that, importantly, are not affected by these issues. Is it
really a good idea to have three different implementations of
essentially the same functionality?

Best wishes,
Mike

  parent reply	other threads:[~2009-12-04  1:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 14:45 Michael Gilbert
     [not found] ` <20091203165321.GB6416@tatooine.rebelbase.local>
2009-12-04  1:53   ` Michael Gilbert [this message]
2009-12-05 19:19     ` Michael Gilbert

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=20091203205311.9a9478e4.michael.s.gilbert@gmail.com \
    --to=michael.s.gilbert@gmail.com \
    --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

Powered by JetHome