From: markus reichelt <mr@lists.notified.de>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: AES cryptoloop corruption under recent -mm kernels
Date: Sun, 1 Feb 2004 20:40:45 +0100 [thread overview]
Message-ID: <20040201194045.GA2372@lists.notified.de> (raw)
In-Reply-To: <20040201171928.GG1254@edu.joroinen.fi>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pasi Kärkkäinen <pasik@iki.fi> wrote:
> http://www.tcs.hut.fi/~mjos/doc/herring061103.pdf
>
> That PDF by Markku-Juhani O. Saarinen discusses about these vulnerabilities,
> and has one solution to them.
Interesting... Do you happen to know where one can get hold of that patch he
mentioned?
I'd like to try it out with the recent 2.6.2-rc3 kernel.
- --
Bastard Administrator in $hell
GPG-Key at http://lists.notified.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAHVY8LMyTO8Kj/uQRAsL3AJwKgmWs1nFx2dyGJvD0LN/1RcMOAQCfUrev
UkVCitUNB2wdW+v6EdlTxHQ=
=As2+
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-02-01 19:41 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
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 [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=20040201194045.GA2372@lists.notified.de \
--to=mr@lists.notified.de \
--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