wpa_supplicant-0.6.9 源码

wpa_supplicant for Windows ========================== Copyright (c) 2003-2009, Jouni Malinen <j@w1.fi> and contributors All Rights Reserved. This program is dual-licensed under both the GPL version 2 and BSD license. Either license may be used at your option. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). wpa_supplicant has support for being used as a WPA/WPA2/IEEE 802.1X Supplicant on Windows. The current port requires that WinPcap (http://winpcap.polito.it/) is installed for accessing packets and the driver interface. Both release versions 3.0 and 3.1 are supported. The current port is still somewhat experimental. It has been tested mainly on Windows XP (SP2) with limited set of NDIS drivers. In addition, the current version has been reported to work with Windows 2000. All security modes have been verified to work (at least complete authentication and successfully ping a wired host): - plaintext - static WEP / open system authentication - static WEP / shared key authentication - IEEE 802.1X with dynamic WEP keys - WPA-PSK, TKIP, CCMP, TKIP+CCMP - WPA-EAP, TKIP, CCMP, TKIP+CCMP - WPA2-PSK, TKIP, CCMP, TKIP+CCMP - WPA2-EAP, TKIP, CCMP, TKIP+CCMP Binary version -------------- Compiled binary version of the wpa_supplicant and additional tools is available from http://w1.fi/wpa_supplicant/. These binaries can be used after installing WinPcap. wpa_gui uses Qt 4 framework and may need additional dynamic libraries (DLLs). These libraries are available from http://w1.fi/wpa_supplicant/qt4/wpa_gui-qt433-windows-dll.zip You can copy the DLL files from this ZIP package into the same directory with wpa_gui.exe to allow wpa_gui to be started. Building wpa_supplicant with mingw ---------------------------------- The default build setup for wpa_supplicant is to use MinGW and cross-compiling from Linux to MinGW/Windows. It should also be possible to build this under Windows using the MinGW tools, but that is not tested nor supported and is likely to require some changes to the Makefile unless cygwin is used. Building wpa_supplicant with MSVC --------------------------------- wpa_supplicant can be built with Microsoft Visual C++ compiler. This has been tested with Microsoft Visual C++ Toolkit 2003 and Visual Studio 2005 using the included nmake.mak as a Makefile for nmake. IDE can also be used by creating a project that includes the files and defines mentioned in nmake.mak. Example VS2005 solution and project files are included in vs2005 subdirectory. This can be used as a starting point for building the programs with VS2005 IDE. Visual Studio 2008 Express Edition is also able to use these project files. WinPcap development package is needed for the build and this can be downloaded from http://www.winpcap.org/install/bin/WpdPack_4_0_2.zip. The default nmake.mak expects this to be unpacked into C:\dev\WpdPack so that Include and Lib directories are in this directory. The files can be stored elsewhere as long as the WINPCAPDIR in nmake.mak is updated to match with the selected directory. In case a project file in the IDE is used, these Include and Lib directories need to be added to project properties as additional include/library directories. OpenSSL source package can be downloaded from http://www.openssl.org/source/openssl-0.9.8i.tar.gz and built and installed following instructions in INSTALL.W32. Note that if EAP-FAST support will be included in the wpa_supplicant, OpenSSL needs to be patched to# support it openssl-0.9.8i-tls-extensions.patch. The example nmake.mak file expects OpenSSL to be installed into C:\dev\openssl, but this directory can be modified by changing OPENSSLDIR variable in nmake.mak. If you do not need EAP-FAST support, you may also be able to use Win32 binary installation package of OpenSSL from http://www.slproweb.com/products/Win32OpenSSL.html instead of building the library yourself. In this case, you will need to copy Include and Lib directories in suitable directory, e.g., C:\dev\openssl for the default nmake.mak. Copy {Win32OpenSSLRoot}\include into C:\dev\openssl\include and make C:\dev\openssl\lib subdirectory with files from {Win32OpenSSLRoot}\VC (i.e., libeay*.lib and ssleay*.lib). This will end up using dynamically linked OpenSSL (i.e., .dll files are needed) for it. Alternative, you can copy files from {Win32OpenSSLRoot}\VC\static to create a static build (no OpenSSL .dll files needed). Building wpa_supplicant for cygwin ---------------------------------- wpa_supplicant can be built for cygwin by installing the needed development packages for cygwin. This includes things like compiler, make, openssl development package, etc. In addition, developer's pack for WinPcap (WPdpack.zip) from http://winpcap.polito.it/install/default.htm is needed. .config file should enable only one driver interface, CONFIG_DRIVER_NDIS. In addition, include directories may need to be added to match the system. An example configuration is available in defconfig. The library and include files for WinPcap will either need to be installed in compiler/linker default directories or their location will need to be adding to .config when building wpa_supplicant. Othen than this, the build should be more or less identical to Linux version, i.e., just run make after having created .config file. An additional tool, win_if_list.exe, can be built by running "make win_if_list". Building wpa_gui ---------------- wpa_gui uses Qt application framework from Trolltech. It can be built with the open source version of Qt4 and MinGW. Following commands can be used to build the binary in the Qt 4 Command Prompt: # go to the root directory of wpa_supplicant source code cd wpa_gui-qt4 qmake -o Makefile wpa_gui.pro make # the wpa_gui.exe binary is created into 'release' subdirectory Using wpa_supplicant for Windows -------------------------------- wpa_supplicant, wpa_cli, and wpa_gui behave more or less identically to Linux version, so instructions in README and example wpa_supplicant.conf should be applicable for most parts. In addition, there is another version of wpa_supplicant, wpasvc.exe, which can be used as a Windows service and which reads its configuration from registry instead of text file. When using access points in "hidden SSID" mode, ap_scan=2 mode need to be used (see wpa_supplicant.conf for more information). Windows NDIS/WinPcap uses quite long interface names, so some care will be needed when starting wpa_supplicant. Alternatively, the adapter description can be used as the interface name which may be easier since it is usually in more human-readable format. win_if_list.exe can be used to find out the proper interface name. Example steps in starting up wpa_supplicant: # win_if_list.exe ifname: \Device\NPF_GenericNdisWanAdapter description: Generic NdisWan adapter ifname: \Device\NPF_{769E012B-FD17-4935-A5E3-8090C38E25D2} description: Atheros Wireless Network Adapter (Microsoft's Packet Scheduler) ifname: \Device\NPF_{732546E7-E26C-48E3-9871-7537B020A211} description: Intel 8255x-based Integrated Fast Ethernet (Microsoft's Packet Scheduler) Since the example configuration used Atheros WLAN card, the middle one is the correct interface in this case. The interface name for -i command line option is the full string following "ifname:" (the "\Device\NPF_" prefix can be removed). In other words, wpa_supplicant would be started with the following command: # wpa_supplicant.exe -i'{769E012B-FD17-4935-A5E3-8090C38E25D2}' -c wpa_supplicant.conf -d -d optional enables some more debugging (use -dd for even more, if needed). It can be left out if debugging information is not needed. With the alternative mechanism for selecting the interface, this command has identical results in this case: # wpa_supplicant.exe -iAtheros -c wpa_supplicant.conf -d Simple configuration example