cfg80211 support for pre-auth

cfg80211 support for pre-auth

[Dhiraj Gaurh]

Hello folks,
 PMK caching and pre-auth are not currently supported by
cfg80211/nl80211/supplicant. Actually the former is only not supported
by wpa_supplicant. I have fixed that and will be moving the code
upstream shortly.
BUT the latter is not even supported by cfg/nl. Anybody working on
that ? Actually support is not even there for using wext in this
scenario. So you just fail certification if you use cfg/nl. I need to
change this scenario.
Currently thinking if it is better to add support in cfg/nl/supplicant
or just use wext stuff and a patch.
I need an API in cfg80211 to let the driver tell cfg that it has got
beacon from another AP it can preauth with. Then the supplicant will
start the pre-auth process when it receives the message.
Currently in wext the IWEVPMKIDCAND is used for this to pass this info
from drivers to supplicant but this framework does not exist for
cfg80211.
After my changes, hopefully you will be able to pass certification by
simply using cfg/nl and removing wext entirely from the picture.
regards
Dhiraj

Re: cfg80211 support for pre-auth

[Johannes Berg]

Hi,

On Fri, 2010-08-13 at 20:10 +0530, Dhiraj Gaurh wrote:
> Hello folks,
>  PMK caching and pre-auth are not currently supported by
> cfg80211/nl80211/supplicant. Actually the former is only not supported
> by wpa_supplicant. I have fixed that and will be moving the code
> upstream shortly.

Sounds good.

> BUT the latter is not even supported by cfg/nl. Anybody working on
> that ? Actually support is not even there for using wext in this
> scenario. So you just fail certification if you use cfg/nl. I need to
> change this scenario.
> Currently thinking if it is better to add support in cfg/nl/supplicant
> or just use wext stuff and a patch.
> I need an API in cfg80211 to let the driver tell cfg that it has got
> beacon from another AP it can preauth with. Then the supplicant will
> start the pre-auth process when it receives the message.

I don't get it. You have the information, it's part of the scan results,
quite obviously. Roaming, and consequently pre-authentication, isn't
triggered by the driver. Or are you thinking about full-mac scenarios?

johannes