aboutsummaryrefslogtreecommitdiffstats
path: root/src/ap/wpa_auth_glue.c
diff options
context:
space:
mode:
authorBadrish Adiga H R <badrish.adigahr@gmail.com>2017-01-06 09:57:10 (GMT)
committerJouni Malinen <j@w1.fi>2017-02-06 19:02:53 (GMT)
commite54691106b29f41aa3081b00eb4f48e411cebc72 (patch)
treeffdb33370e01ca59ea33ca76b8ada7472d34870c /src/ap/wpa_auth_glue.c
parent7faf403f9fb39fea9a0545025cc284ef05e022a7 (diff)
downloadhostap-e54691106b29f41aa3081b00eb4f48e411cebc72.zip
hostap-e54691106b29f41aa3081b00eb4f48e411cebc72.tar.gz
hostap-e54691106b29f41aa3081b00eb4f48e411cebc72.tar.bz2
mka: Some bug fixes for MACsec in PSK mode
Issue: ------ The test setup has 2 peers running MACsec in PSK mode, Peer A with MAC address higher than MAC Address of peer B. Test sequence is 1. Peer B starts with actor_priority 255 2. Peer A starts with priority 16, becomes key server. 3. Peer A stops.. 4. Peer A restarts with priority 255, but because of the stale values participant->is_key_server(=TRUE) and participant->is_elected(=TRUE) it continues to remain as Key Server. 5. For peer B, key server election happens and since it has lower MAC address as compared to MAC address of A, it becomes the key server. Now we have 2 key servers in CA and is not correct. Root-cause & fix: ----------------- When number of live peers become 0, the flags such lrx, ltx, orx, otx, etc. need to be cleared. In MACsec PSK mode, these stale values create problems while re-establishing CA. Signed-off-by: Badrish Adiga H R <badrish.adigahr@gmail.com>
Diffstat (limited to 'src/ap/wpa_auth_glue.c')
0 files changed, 0 insertions, 0 deletions