From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Andrew Morton <akpm@osdl.org>
Cc: michal@logix.cz, jmorris@redhat.com, davem@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Support for VIA PadLock crypto engine
Date: Thu, 13 May 2004 22:02:17 +0300 [thread overview]
Message-ID: <40A3C639.4FD98046@users.sourceforge.net> (raw)
In-Reply-To: 20040513113028.085194a3.akpm@osdl.org
Andrew Morton wrote:
> Jari Ruusu <jariruusu@users.sourceforge.net> wrote:
> > The cryptoloop implementation is busted in more than one way, so it is
> > useless for security needs:
>
> Is dm-crypt any better?
Nope. dm-crypt has same exploitable cryptographic flaws.
--
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-05-13 19:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 14:40 [PATCH 2/2] Support for VIA PadLock crypto engine Michal Ludvig
2004-05-10 15:55 ` James Morris
2004-05-10 19:23 ` Michal Ludvig
2004-05-11 16:56 ` [PATCH 1/2] " Michal Ludvig
2004-05-12 8:55 ` Michal Ludvig
2004-05-11 16:56 ` [PATCH 2/2] " Michal Ludvig
2004-05-12 13:37 ` James Morris
2004-05-12 14:42 ` Michal Ludvig
2004-05-12 14:52 ` James Morris
2004-05-12 15:25 ` Michal Ludvig
2004-05-13 0:44 ` James Morris
2004-05-14 15:10 ` New list for CryptoAPI development Michal Ludvig
2004-05-17 8:39 ` Arnd Bergmann
2004-05-17 8:53 ` Michal Ludvig
2004-05-13 12:59 ` [PATCH 2/2] Support for VIA PadLock crypto engine Jari Ruusu
2004-05-13 18:30 ` Andrew Morton
2004-05-13 19:02 ` Jari Ruusu [this message]
2004-05-13 20:00 ` Michal Ludvig
2004-05-14 13:31 ` Jari Ruusu
2004-05-14 14:09 ` Fruhwirth Clemens
2004-05-14 16:05 ` Jari Ruusu
2004-05-16 15:32 ` Fruhwirth Clemens
2004-05-16 17:46 ` Jari Ruusu
2004-05-11 17:04 ` [PATCH 3/2 :-] " Michal Ludvig
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=40A3C639.4FD98046@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@logix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.