From: Bradley Chapman <kakadu_croc@yahoo.com>
To: Jouni Malinen <jkmaline@cc.hut.fi>
Cc: Netdev <netdev@oss.sgi.com>,
hostap@shmoo.com, Jeff Garzik <jgarzik@pobox.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jean Tourrilhes <jt@bougret.hpl.hp.com>,
prism54-devel@prism54.org
Subject: Re: Prism54 WPA Support - wpa_supplicant - Linux general wpa support
Date: Thu, 3 Jun 2004 04:05:06 -0700 (PDT) [thread overview]
Message-ID: <20040603110506.3996.qmail@web40904.mail.yahoo.com> (raw)
In-Reply-To: <20040603034458.GD7548@jm.kir.nu>
To all,
I'm sorry to break into this thread, but I was just curious as to what will
eventually happen to wpa_supplicant. Based upon Mr. Malinen's words, as well as what
a few others in this thread have been saying, will WPA and 802.1x eventually become
generalized driver frameworks in the kernel (like MII), using the current Crypto API
and crypto drivers?
I'm just asking from an enduser perspective here, because eventually I will be
purchasing an 802.11g Prism54 device and would like to have an idea of the relative
ease of configuring 802.1x and WPA in the future.
Thanks,
Brad
=====
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
next prev parent reply other threads:[~2004-06-03 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 7:14 Prism54 WPA Support - wpa_supplicant - Linux general wpa support Luis R. Rodriguez
2004-06-02 13:23 ` Jouni Malinen
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 [this message]
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=20040603110506.3996.qmail@web40904.mail.yahoo.com \
--to=kakadu_croc@yahoo.com \
--cc=hostap@shmoo.com \
--cc=jgarzik@pobox.com \
--cc=jkmaline@cc.hut.fi \
--cc=jt@bougret.hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).