From: Myrddin Ambrosius <imipak@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Linux crypto?
Date: Wed, 22 May 2002 11:03:50 -0700 (PDT) [thread overview]
Message-ID: <20020522180350.28170.qmail@web12307.mail.yahoo.com> (raw)
I noticed that Motorola has published a set of tech
docs for their S1-range of crypto co-processors, which
look pretty comprehensive. (The 190 looks to be a very
nice chip, which -as best as I can tell- just plugs
straight onto a PCI bus.) Other co-pro manufacturers
(such as HIFN) seem to also have humungous tech
manuals for their crypto chips.
Is anyone working on drivers for these beasties?
Alongside that, I also noticed that many manufacturers
(again, Motorola and HIFN seem to top the list)
working on network accelerator chips - some h/w
L2/L3/L4 queueing/filtering, rudimentary packet
mangling, etc. Linux already has most of the
interesting stuff from the chips I've looked at, and
in most places is way more advanced in what it can do/
Given the ipfilter design, would there be any way to
use those chips as an additional networking layer?
(And, just as importantly, would there be any point?)
Secondly, I've taken a look at the "International
Kernel Patch" for Linux. I have finally found a
(fairly) mainstream kernel patch that is updated less
frequently than my own FOLK patch! Also, nobody seems
to use it. Packages that use crypto seem to steer
towards openssl, rsa-ref, mcrypt/mhash/gcrypt, gnutls,
and/or or private implementations. Even FreeS/WAN and
USAGI take no advantage of anything in the IKP.
Ignoring, for a second, the US export laws (which are
no longer an issue, anyway), is there some fundamental
reason why the IKP seems to be ignored? If there is,
then does anyone know of any re-design/re-write
effort?
__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com
next reply other threads:[~2002-05-22 18:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 18:03 Myrddin Ambrosius [this message]
2002-05-22 18:38 ` Linux crypto? Alan Cox
2002-05-23 8:45 ` Trond Myklebust
2002-05-23 21:46 ` Tobias Ringstrom
2002-05-24 14:58 ` Alan Cox
2002-05-24 17:32 ` Thomas 'Dent' Mirlacher
2002-05-24 17:21 ` David S. Miller
2002-05-24 17:42 ` Thomas 'Dent' Mirlacher
2002-05-24 17:31 ` David S. Miller
2002-05-24 17:57 ` Thomas 'Dent' Mirlacher
2002-05-24 19:18 ` Myrddin Ambrosius
2002-05-25 4:01 ` Henrique de Moraes Holschuh
2002-05-24 18:41 ` Alan Cox
2002-05-24 18:30 ` Thomas 'Dent' Mirlacher
2002-05-24 18:55 ` Alan Cox
2002-05-24 18:50 ` Sandy Harris
2002-05-29 0:24 ` Petro
2002-05-24 20:17 ` Myrddin Ambrosius
2002-05-24 21:25 ` Thomas 'Dent' Mirlacher
2002-05-24 18:45 ` Herman Oosthuysen
2002-05-24 21:49 ` Xavier Bestel
2002-05-24 21:43 ` David S. Miller
2002-05-26 10:06 ` Jakob Østergaard
2002-06-18 15:06 ` Drivers, Hardware, and their relationship to Bagels Myrddin Ambrosius
2002-06-18 15:01 ` Zwane Mwaikambo
2002-06-18 15:26 ` Richard B. Johnson
2002-06-18 18:35 ` Myrddin Ambrosius
2002-06-18 19:13 ` Richard B. Johnson
2002-06-19 2:11 ` Stevie O
2002-06-18 16:01 ` Xavier Bestel
2002-06-18 18:23 ` Myrddin Ambrosius
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 18:28 Linux crypto? James Yonan
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=20020522180350.28170.qmail@web12307.mail.yahoo.com \
--to=imipak@yahoo.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