mirror of
https://github.com/vanhoefm/fragattacks.git
synced 2024-11-26 01:08:22 -05:00
8b2b2a70ef
If we discover a P2P peer based on a Beacon frame from the GO role, we do not get information about the supported configuration methods. This can result in issues if the P2P managing entity above wpa_supplicant is not prepared to handling config_methods=0x0. To avoid this, postpone reporting of the P2P-DEVICE-FOUND event when this happens on one of the social channels. It would be good to be able to this on all channels, but that could result in issues of never indicating the event for a peer that is operating a GO on a channel that requires passive scanning. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com> |
||
---|---|---|
.. | ||
ap | ||
common | ||
crypto | ||
drivers | ||
eap_common | ||
eap_peer | ||
eap_server | ||
eapol_auth | ||
eapol_supp | ||
l2_packet | ||
p2p | ||
radius | ||
rsn_supp | ||
tls | ||
utils | ||
wps | ||
lib.rules | ||
Makefile |