> this is perfectly fine. before communication can start, sequence numbers > need to get synchronized to avoid replay attacks. this will cause code to enter wpa_ft_rrb_build(key, key_len, NULL, NULL, seq_req_auth, NULL) and try to allocate '0' length memory. I will try to compile and run with the mentioned (-O0 and -ggdb and running gdb) but not sure when i can do it. I tested with iphoneSE.May be u can give a try. Thanks, On Thu, Jan 24, 2019 at 1:58 AM michael-dev <michael-dev@xxxxxxxxxxxxx> wrote: > > Am 23.01.2019 21:05, schrieb Abc Abc: > > wpa_key_mgmt=WPA-PSK > > shouldn't this include FT-PSK as well? Otherwise FT should not happen > anyway. > > Additionally, with PSK, you can avoid using push/pull msg using > ft_psk_generate_local. > > > For pmk-R1 push mechanism, In wpa_ft_rrb_seq_chk(), checks for "if > > (rkh_seq->rx.num_last == 0)" this is always true as "rkh_seq" is just > > allocated and set to '0'. This causes wpa_ft_rrb_seq_chk() to returns > > "DEFER". > > this is perfectly fine. before communication can start, sequence numbers > need to get synchronized to avoid replay attacks. > > > wpa_ft_rrb_rx_push() --- ( for some reason, AP-AP comm changed from > > pull (while reporting bug) to push(while debugging) during my testing) > > See pmk_r1_push. Pushing only happens if enabled and during r0 > negotiation. > Pull happens if no matching push is received. > > Can you provide more details about the crash, e.g. by building hostapd > with > -O0 and -ggdb and running it using gdb? > > > Does any hostapd configuration changes are required to support "seq > > num" ? > > It is expected to work out of the box. > > Regards, > M. Braun _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
