aboutsummaryrefslogtreecommitdiffstats
path: root/tests
diff options
context:
space:
mode:
authorMichael Braun <michael-dev@fami-braun.de>2016-09-24 20:53:42 (GMT)
committerJouni Malinen <j@w1.fi>2016-10-09 08:57:56 (GMT)
commit96590564d658cf344778e9c84bcd58d39764e11d (patch)
tree05a794a163890314b0bf11fa492cf025deeb5697 /tests
parenta25e4efc9e428d968e83398bd8c9c94698ba5851 (diff)
downloadhostap-96590564d658cf344778e9c84bcd58d39764e11d.zip
hostap-96590564d658cf344778e9c84bcd58d39764e11d.tar.gz
hostap-96590564d658cf344778e9c84bcd58d39764e11d.tar.bz2
FT: Allow PMK-R0 and PMK-R1 for FT-PSK to be generated locally
Station should be able to connect initially without ft_pmk_cache filled, so the target AP has the PSK available and thus the same information as the origin AP. Therefore neither caching nor communication between the APs with respect to PMK-R0 or PMK-R1 or VLANs is required if the target AP derives the required PMKs locally. This patch introduces the generation of the required PMKs locally for FT-PSK. Additionally, PMK-R0 is not stored (and thus pushed) for FT-PSK. So for FT-PSK networks, no configuration of inter-AP communication is needed anymore when using ft_psk_generate_local=1 configuration. The default behavior (ft_psk_generate_local=0) remains to use the pull/push protocol. Signed-off-by: Michael Braun <michael-dev@fami-braun.de>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions