On 22/04/2017 10:46, Michael Braun wrote: > Convert FT RRB into a new TLV based format. Use AES-SIV as AEAD cipher > to protect the messages. > > This needs at least 32 byte long keys. These can be provided either > by a config file change or letting a KDF derive the 32 byte key used > from the 16 byte key given. > > This breaks backward compatibility, i.e., hostapd needs to be updated on > all APs at the same time to allow FT to remain functional. > > Signed-off-by: Michael Braun <michael-dev@xxxxxxxxxxxxx> Hello, This commit and 1/8 breaks the build of wpa_supplicant if one enables CONFIG_IEEE80211R_AP, since you forgot to update the wpa_supplicant build system. The build failure look like this: ../src/ap/wpa_auth_ft.o: In function `wpa_ft_rrb_encrypt': wpa_supplicant/../src/ap/wpa_auth_ft.c:298: undefined reference to `aes_siv_encrypt' ../src/ap/wpa_auth_ft.o: In function `wpa_ft_rrb_decrypt': wpa_supplicant/../src/ap/wpa_auth_ft.c:96: undefined reference to `aes_siv_decrypt' collect2: error: ld returned 1 exit status It is also possible that it does not work at runtime, since you added initialization code in hostapd and not in wpa_supplicant. At first glance, it seems wpa_supplicant does not have a hostapd_interfaces structure, and hapd->iface->interfaces seems to be NULL. In my case, CONFIG_IEEE80211R_AP was enabled by accident, so disabling it fixes it. But i think this issue deserve a fix. _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
