<div>Hi Jouni,</div><div><br></div><div>Please, as per your reply , help me with following queries :</div><div><br></div><div>1.<span class="" style="white-space:pre"> </span>The PSK matching code in SM_STATE(WPA_PTK, PTKCALCNEGOTIATING) in src/ap/wpa_auth.c would need some changes to make it match the P2P Client </div>
<div> case based on P2P Device Address instead of the P2P Interface Address.<br></div><div><br></div><div> --Currently, complete flow for SM_STATE(WPA_PTK, PTKCALCNEGOTIATING) is based on P2P Interface Address and struct wpa_state_machine stores the </div>
<div> interface address. Hence, storing P2P Device Address in struct wpa_ssid is not helping either.</div><div><br></div><div><br></div><div>2.<span class="" style="white-space:pre"> </span><span style="white-space:pre">Store the P2P Device Address with the runtime network (struct wpa_ssid)
</span></div><div><span style="white-space:pre"> --What is the significance of storing P2P Device Address in struct wpa_ssid?</span></div><span style="white-space:pre"> </span><div><span style="white-space:pre"><br>
</span><div><br></div><div>3.<span class="" style="white-space:pre"> </span>Disconnecting a client part would then be to remove the identified address, PSK pair and deauthenticate the station from the group.</div><div><br>
</div><div> --Currently, supplicant first deauthenticate and once it receives event EVENT_DISASSOC from driver then it removes the identified address, PSK pair. </div><div><br></div><div>4. Per device PSK changes also requires changes for validating data frame based on PSK.</div>
<div><br></div><div>Correct me if I am wrongly understood. Also, further guide would be appreciated.</div><div><br></div><div>Regards,</div><div>Nishant</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Sun, Nov 11, 2012 at 7:49 PM, Jouni Malinen <span dir="ltr"><<a href="mailto:j@w1.fi" target="_blank">j@w1.fi</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, Nov 06, 2012 at 12:50:50PM +0530, Nishant Sharma wrote:<br>
> As per my understanding currently, same PSK is being shared<br>
> for all the clients of the same GO. Your suggestion is to have one PSK per<br>
> client. But my requirement is to disconnect a particular client form GO.<br>
> Can I achieve this from following steps:<br>
> 1. Adding a new command for client disconnect in interface.<br>
> 2. this disconnect command will send a disassociation frame to that client.<br>
> 3. Remove client from peer list and clean up all the client resources from<br>
> supplicant of GO.<br>
<br>
</div>That will not prevent the disconnected peer from connecting again since<br>
it knows the PSK. Per-device PSK needs to be used to allow this<br>
operation to be done securely.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Jouni Malinen PGP id EFC895FA<br>
_______________________________________________<br>
HostAP mailing list<br>
<a href="mailto:HostAP@lists.shmoo.com">HostAP@lists.shmoo.com</a><br>
<a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Thanks and Regards<br>Nishant Sharma<br><br>
</div>