From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Jim Faulkner <jfaulkne@ccs.neu.edu>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: PROBLEM: AES cryptoloop corruption under recent -mm kernels
Date: Thu, 15 Jan 2004 18:57:09 +0200 [thread overview]
Message-ID: <4006C665.3065DFA1@users.sourceforge.net> (raw)
In-Reply-To: Pine.GSO.4.58.0401141357410.10111@denali.ccs.neu.edu
Jim Faulkner wrote:
> I am experiencing data corruption on my AES cryptoloop partition under
> recent -mm kernels (including 2.6.1-mm3). I am unsure how long this
> problem has existed, and I am unsure if this problem exists in the
> mainstream kernel (I can't test it because of an aic7xxx bug in the
> mainstream kernel).
This bug is fixed in loop-AES package. In addition to this bug fix it fixes
many other bugs as well, and achieves correct write ordering when used with
journaling file systems.
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v2.0d.tar.bz2
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v2.0d.tar.bz2.sign
Jim,
If you want your data secure, you need to re-encrypt your data anyway.
Mainline loop crypto implementation has exploitable vulnerability that is
equivalent to back door. Kerneli.org folks have always shipped back-doored
loop crypto, and now mainline folks are shipping back-doored loop crypto.
Kerneli.org derivatives such as Debian, SuSE, and others are also
back-doored.
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
next prev parent reply other threads:[~2004-01-15 16:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 20:36 PROBLEM: AES cryptoloop corruption under recent -mm kernels Jim Faulkner
2004-01-14 20:41 ` Jim Faulkner
2004-01-14 20:52 ` Andrew Morton
2004-01-14 23:30 ` Jim Faulkner
2004-01-15 2:44 ` Matthias Hentges
2004-01-15 16:57 ` Jari Ruusu [this message]
2004-01-15 17:24 ` Jim Faulkner
2004-01-15 20:33 ` Jari Ruusu
2004-01-15 22:59 ` Hans Reiser
2004-01-16 14:21 ` Mark Borgerding
2004-01-16 15:42 ` James Morris
2004-01-16 17:10 ` Mark Borgerding
2004-01-17 2:47 ` David Wagner
2004-01-17 16:13 ` Mark Borgerding
2004-01-17 20:39 ` Shawn Willden
[not found] ` <4007EBDA.2060308@borgerding.net>
[not found] ` <4007F79C.80A5DE72@users.sourceforge.net>
[not found] ` <400818AA.9080009@borgerding.net>
2004-01-16 21:43 ` Jari Ruusu
2004-01-15 18:16 ` James Morris
2004-02-01 17:19 ` Pasi Kärkkäinen
2004-02-01 19:40 ` markus reichelt
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=4006C665.3065DFA1@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=akpm@osdl.org \
--cc=jfaulkne@ccs.neu.edu \
--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