From: Johannes Berg <johannes@sipsolutions.net>
To: Matt Chen <machen@suse.com>
Cc: linux-wireless@vger.kernel.org, Michal Marek <MMarek@suse.com>,
oneukum@suse.de, tiwai@suse.de
Subject: Re: WLAN EAP methods verification.
Date: Thu, 06 Jun 2013 09:14:08 +0200 [thread overview]
Message-ID: <1370502848.8401.1.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <51B099FE0200009200022E0D@soto.provo.novell.com> (sfid-20130606_061746_887758_9E445931)
On Wed, 2013-06-05 at 22:17 -0600, Matt Chen wrote:
> I would like to ask if there is a policy or way to verify a WLAN
> driver in kernel such as ath9k, iwlwifi, rt2x00 or rtlwifi and so
> on ... pass all the EAP method [1] or WPA/WPA2 encryption ?
Not really. I think we all pretty much assume that once we support the
cipher algorithms (TKIP/CCMP) everything else works because it's
implemented in wpa_supplicant and the drivers don't have to do anything
but pass frames and eventually install keys.
The only driver where that's not true is the PS3 wifi driver ;-)
johannes
prev parent reply other threads:[~2013-06-06 7:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 4:17 WLAN EAP methods verification Matt Chen
2013-06-06 7:14 ` Johannes Berg [this message]
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=1370502848.8401.1.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=MMarek@suse.com \
--cc=linux-wireless@vger.kernel.org \
--cc=machen@suse.com \
--cc=oneukum@suse.de \
--cc=tiwai@suse.de \
/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