NAI on reconnection
Sun Aug 10 01:47:38 PDT 2014
The SessID need not be stored over restarts. What I was hoping is that the
first time I use the NAI as abc at example.com but for reauthentication I use
abc at example.com+sessid.
Should this be supplied in the init_for_reauth() method somehow?
On Sun, Aug 10, 2014 at 11:00 AM, Jouni Malinen <j at w1.fi> wrote:
> On Sat, Aug 09, 2014 at 08:25:30PM +0300, khali singh wrote:
> > I have implemented a new EAP method. It works fine for the first
> > attempt and upon providing proper credentials, a supplicant can
> > successfully complete the handshake and receive the PMK.
> > But now I want to handle the case when the key expires. And I want to do
> > abbreviated handshake based on the previous exchange. So I want to send
> > SessID (session ID) along with the original NAI that was used.
> > But I understood that the NAI is specified in the configuration file of
> > supplicant and not in the EAP method. How do I append a SessID to the NAI
> > before it is sent over the network. Note, this should only be done if
> > has been a previous successful handshake before.
> If you do not need to store the SessID over wpa_supplicant restarts, you
> can maintain this within the EAP peer method (see deinit_for_reauth() and
> init_for_reauth() callbacks).
> Or are you referring to using EAP-Identity method instead of EAP
> messages specific to this new EAP method? If so, use the get_identity()
> 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