From: Michael Gilbert <michael.s.gilbert@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: CVE-2004-2135 and CVE-2004-2136
Date: Wed, 2 Dec 2009 09:45:39 -0500 [thread overview]
Message-ID: <20091202094539.c1184899.michael.s.gilbert@gmail.com> (raw)
Hi,
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. The paper [2] indicates that the
disclosing team developed a 3,000 line patch, but I have been unable to
track this down to determine whether or not it has been applied. There
is also this more current write-up [3], which is rather revealing. Have
these issues slipped through the cracks? Thanks upfront for any info on
the matter.
Best wishes,
Mike
[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-2135
[1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-2136
[2] http://mareichelt.de/pub/notmine/diskenc.pdf
[3] http://mareichelt.de/pub/texts.cryptoloop.php?alt_styles=2
next reply other threads:[~2009-12-02 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 14:45 Michael Gilbert [this message]
[not found] ` <20091203165321.GB6416@tatooine.rebelbase.local>
2009-12-04 1:53 ` Michael Gilbert
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=20091202094539.c1184899.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