mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jouni Malinen <jkmaline@cc.hut.fi>
To: "Luis R. Rodriguez" <mcgrof@studorgs.rutgers.edu>
Cc: Netdev <netdev@oss.sgi.com>,
	hostap@shmoo.com, prism54-devel@prism54.org,
	Jeff Garzik <jgarzik@pobox.com>,
	Jean Tourrilhes <jt@bougret.hpl.hp.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Prism54 WPA Support - wpa_supplicant - Linux general wpa support
Date: Wed, 2 Jun 2004 06:23:14 -0700	[thread overview]
Message-ID: <20040602132313.GB7341@jm.kir.nu> (raw)
In-Reply-To: <20040602071449.GJ10723@ruslug.rutgers.edu>

On Wed, Jun 02, 2004 at 03:14:49AM -0400, Luis R. Rodriguez wrote:

> I'm glad wpa_supplicant exists :). Interacting with it *is* our missing
> link to getting full WPA support (great job Jouni). In wpa_supplicant 
> cvs I see a base code for driver_prism54.c (empty routines, just providing skeleton).
> Well I'll be diving in it now and see where I can get. If anyone else is
> interested in helping with WPA support for prism54, working with
> wpa_supplicant is the way to go.

I have a bit more code for this in my work directory somewhere (setting
the WPA IE and a new ioctl for this for the driver). I did not submit
these yet since the extended MLME mode was not working and the changes
were not yet really working properly. I can try to find these patches
somewhere.. Anyway, I would first like to see the extended MLME mode
working with any (even plaintext) AP and then somehow add the WPA IE to
the AssocReq. After that, it should be only TKIP/CCMP key configuration
and that's about it..

> I'm curious though -- wpa_supplicant is pretty much userspace. This was
> done with good intentions from what I read but before we get dirty 
> with wpa_supplicant I'm wondering if we should just integrate a lot of 
> wpa_supplicant into kernel space (specifically wireless tools).

Why? Which functionality would you like to move into kernel? Not that
I'm against moving some parts, but I would certainly like to hear good
reasons whenever moving something to kernel space if it can be done (or
in this case, has already been done) in user space..

> Regardless, as Jouni points out, there is still a framework for WPA that needs
> to be written for all linux wireless drivers, whether it's to assist
> wpa_supplicant framework or to integrate wpa_supplicant into kernel space.

The first thing I would like to see is an addition to  Linux wireless
extensions for WPA/WPA2 so that we can get rid of the private ioctls in
the drivers. Even though these can often be similar, it would be nice to
just write one driver interface code in wpa_supplicant and have it
working with all Linu drivers.. I hope to find some time to write a
proposal for this.

-- 
Jouni Malinen                                            PGP id EFC895FA

  reply	other threads:[~2004-06-02 13:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-02  7:14 Luis R. Rodriguez
2004-06-02 13:23 ` Jouni Malinen [this message]
2004-06-02 15:55   ` Luis R. Rodriguez
2004-06-03  1:40     ` Jouni Malinen
2004-06-03  2:38       ` Pedro Ramalhais
2004-06-03  3:44         ` Jouni Malinen
2004-06-03 11:05           ` Bradley Chapman
2004-06-03 16:52     ` Jean Tourrilhes
2004-06-04  2:33       ` Jouni Malinen
2004-06-04 18:01         ` Jean Tourrilhes
2004-06-03  4:06   ` Jeff Garzik
2004-06-03 17:07     ` Jean Tourrilhes
2004-06-02 16:28 ` Sam Leffler

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=20040602132313.GB7341@jm.kir.nu \
    --to=jkmaline@cc.hut.fi \
    --cc=hostap@shmoo.com \
    --cc=jgarzik@pobox.com \
    --cc=jt@bougret.hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@studorgs.rutgers.edu \
    --cc=netdev@oss.sgi.com \
    --cc=prism54-devel@prism54.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®