mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jouni Malinen <jkmaline@cc.hut.fi>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
	jt@hpl.hp.com,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@digeo.com>,
	David Gibson <hermes@gibson.dropbear.id.au>,
	Benjamin Reed <breed@almaden.ibm.com>,
	Javier Achirica <achirica@ttd.net>,
	James Morris <jmorris@intercode.com.au>
Subject: Re: CryptoAPI and WEP/stream ciphers (was: airo and firmware upload)
Date: Wed, 14 May 2003 21:21:43 -0700	[thread overview]
Message-ID: <20030515042143.GA1918@jm.kir.nu> (raw)
In-Reply-To: <3EC2D6FB.5050700@pobox.com>

On Wed, May 14, 2003 at 07:53:31PM -0400, Jeff Garzik wrote:

> airo and HostAP do indeed need to use CryptoAPI not reimplement their 
> own crypto, though...

I tried to change my WEP implementation to use CryptoAPI, but that ended
up in problems.. If I understood correctly, current CryptoAPI supports
only block ciphers(?). However, WEP uses RC4 as a stream cipher. This
does not seem to fit the cipher definition in CryptoAPI. One might be
able to implement it as an compression algorithm (encrypt as decompress,
since it adds IV and ICV; and decrypt as compress). However, this
certainly does not sound very reasonable.. Another alternative would be
to add support for stream ciphers into CryptoAPI.

Do you think that it would still be required to get rid of the own WEP
implementation in the Host AP driver before including it into the kernel
tree? Would this mean that someone would first need to add support for
stream ciphers into CryptoAPI? Any change of that happening for Linux
2.6.x?

And one more question before using more time with WEP implementation..
Is someone already working with stream cipher support for CryptoAPI?

-- 
Jouni Malinen                                            PGP id EFC895FA

  parent reply	other threads:[~2003-05-15  4:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 21:12 2.6 must-fix list, v3 Jean Tourrilhes
2003-05-14 22:06 ` airo and firmware upload (was Re: 2.6 must-fix list, v3) Jeff Garzik
2003-05-14 23:32   ` Jean Tourrilhes
2003-05-14 23:38     ` Andrew Morton
2003-05-15  1:04       ` David Gibson
2003-05-16  7:27         ` Manuel Estrada Sainz
2003-05-14 23:43     ` Dave Jones
2003-05-14 23:53       ` Jeff Garzik
2003-05-15  0:59         ` Jouni Malinen
2003-05-15  2:20           ` Jean Tourrilhes
2003-05-15  6:16             ` James Morris
2003-05-15  1:02         ` Jean Tourrilhes
2003-05-15  4:21         ` Jouni Malinen [this message]
2003-05-15  6:04           ` CryptoAPI and WEP/stream ciphers (was: airo and firmware upload) James Morris
2003-05-15  0:55       ` airo and firmware upload (was Re: 2.6 must-fix list, v3) Jean Tourrilhes
2003-05-15  7:13     ` Greg KH
2003-05-15 17:24       ` Jean Tourrilhes
2003-05-15 17:46         ` Greg KH
2003-05-15 19:55           ` Jean Tourrilhes
2003-05-15 20:10             ` Greg KH
2003-05-17 16:58 ` 2.6 must-fix list, v3 Pavel Machek

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=20030515042143.GA1918@jm.kir.nu \
    --to=jkmaline@cc.hut.fi \
    --cc=achirica@ttd.net \
    --cc=akpm@digeo.com \
    --cc=breed@almaden.ibm.com \
    --cc=davej@codemonkey.org.uk \
    --cc=hermes@gibson.dropbear.id.au \
    --cc=jgarzik@pobox.com \
    --cc=jmorris@intercode.com.au \
    --cc=jt@hpl.hp.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

all inboxes | Powered by JetHome®