How digsrc/wpa_supplicant works
Project type and purpose
• This is a low‐level networking/security software suite implementing IEEE 802.11 authentication and key management for both the “supplicant” (client) side (wpa_supplicant) and the “authenticator” (access point) side (hostapd).
• The top‐level contains an HS2.0 (“Hotspot 2.0”) Android client, a monolithic “src” tree with hostapd engine modules, and a separate wpa_supplicant subdirectory with its own UI, control interface, and daemon logic.
File structure
• Top‐level directories:
• hs20/client – HS2.0 Android/Oma‑Dm/OSU client code
• src/ap – hostapd core (AP MLME, beaconing, WPA/WPA2/HS20 logic)
• src/common, crypto, utils – shared libraries (crypto primitives, state‐machines, logging, event loops)
• src/drivers – driver abstraction layer (nl80211, wext, NDIS, BSD, Linux ioctl, privsep)
• src/eap_* – EAP code split into common, peer (supplicant), and server (authenticator)
• src/eapol_* – EAPOL state machines (IEEE 802.1X LAN authentication)
• src/radius – RADIUS client/server (hostapd→RADIUS server)
• src/p2p, src/wps, src/fst, src/pae, src/l2_packet, src/tls, src/rsn_supp – optional feature modules
• wpa_supplicant – wpa_supplicant daemon, control‐iface (CLI, UNIX socket, UDP, Windows named pipe, D-Bus), optional GUI (Qt4), examples, tests.
README for additional insights
• The top‐level README explains that you pick either hostapd or wpa_supplicant (or both), configure via .config, then build in the respective subfolder.
• Detailed descriptions of supported features, platform targets (Linux, Windows, Android), and licensing are in the per‑subdirectory README files.
Detail
• Feature plugins (wps, p2p, hs20) as attachable blocks to the core daemons.
• Event loop interaction (utils/eloop) driving the entire system.