From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: Andi Kleen <ak@muc.de>, Linus Torvalds <torvalds@osdl.org>,
Florian Bohrer <florian.bohrer@t-online.de>,
linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [PATCH] AES x86-64-asm impl.
Date: Mon, 4 Oct 2004 14:35:26 +0200 [thread overview]
Message-ID: <4d8e3fd3041004053560c0f711@mail.gmail.com> (raw)
In-Reply-To: <416142DD.54E0E417@users.sourceforge.net>
On Mon, 04 Oct 2004 15:32:29 +0300, Jari Ruusu
<jariruusu@users.sourceforge.net> wrote:
> Paolo Ciarrocchi wrote:
> > On Mon, 04 Oct 2004 15:20:43 +0300, Jari Ruusu
> > I understand that, I still don't understand the reaseon.
> > But hey, feel free to ignore my question ;)
>
> You haven't looked at cryptoloop security, have you?
No at all.
> No sane person wants to be accociated with that kind of broken and
> backdoored scam. I certainly don't.
It was just curiosity ;)
Thank you for the answer.
--
Paolo
Personal home page: www.ciarrocchi.tk
See my photos: http://paolociarrocchi.fotopic.net/
Buy cool stuff here: http://www.cafepress.com/paoloc
next prev parent reply other threads:[~2004-10-04 12:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2KWl4-wq-25@gated-at.bofh.it>
2004-10-02 19:41 ` [PATCH] AES x86-64-asm impl Andi Kleen
2004-10-04 2:15 ` dean gaudet
2004-10-04 11:51 ` Jari Ruusu
2004-10-04 12:09 ` Paolo Ciarrocchi
2004-10-04 12:20 ` Jari Ruusu
2004-10-04 12:23 ` Paolo Ciarrocchi
2004-10-04 12:32 ` Jari Ruusu
2004-10-04 12:35 ` Paolo Ciarrocchi [this message]
2004-10-04 18:58 ` [discuss] " Raul Miller
2004-10-04 19:26 ` Bill Davidsen
2004-10-04 21:20 ` Lee Revell
2004-10-05 15:00 ` Bill Davidsen
2004-10-04 13:08 ` Andi Kleen
2004-10-05 0:35 ` Andy Lutomirski
2004-10-05 5:15 ` Linus Torvalds
2004-10-02 17:53 Florian Bohrer
2004-10-02 19:37 ` Lee Revell
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=4d8e3fd3041004053560c0f711@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=ak@muc.de \
--cc=discuss@x86-64.org \
--cc=florian.bohrer@t-online.de \
--cc=jariruusu@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 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.