wpa_supplicant WPA Enterprise connecting with wrong credentials
raganaresh.thatha at gmail.com
Tue Jan 31 07:06:16 EST 2012
As you said I have tried with hostap.git development tree.This is not
working for my case.
This is working for the case if we modify or remove the network block then
it is flushing PMKSA cache created using that network block.I have seen the
commit log of this scenario and pasting here for your reference.
But my case is different.First I am connecting with right EAP profile(all
credentials are correct).Then disconnect and selecting the wrong EAP
profile(ssid is same but some credentials are incorrect).I think in this
scenario also,it should not use PMKSA cache and go for new EAP
What is your suggestion?
Thanks for your effort,
On Sat, Jan 28, 2012 at 3:10 PM, Jouni Malinen <j at w1.fi> wrote:
> On Mon, Jan 23, 2012 at 08:18:34PM +0530, raga naresh wrote:
> > >Which version of wpa_supplicant are you using? There has been some
> > >recent changes in the PMKSA caching implementation that forces the
> > >cached credentials to be cleared in various cases. Without those, this
> > >type of connection is quite possible using PMKSA caching that does
> > >indeed skip the EAP authentication.
> > I am using the latest stable release wpa_supplicant-0.7.3. Is there any
> > patch for the recent changes or should I use any other version?
> I don't think these changes change been included in any formal release,
> so you would need to take a snapshot from either the 1.x branch or the
> current development tree (hostap.git).
> Jouni Malinen PGP id EFC895FA
> HostAP mailing list
> HostAP at lists.shmoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HostAP