index.html 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
  2. <html>
  3. <head>
  4. <title>hostapd: IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator</title>
  5. <meta name="description" content="hostapd (IEEE 802.1X, WPA, WPA2, RSN, IEEE 802.11i Authenticator and RADIUS authentication server)">
  6. <meta name="keywords" content="WPA, WPA2, IEEE 802.11i, IEEE 802.1X, WPA Authenticator, hostapd, TKIP, CCMP, EAP-PEAP, EAP-TLS, EAP-TTLS, EAP-SIM, EAP-AKA, EAP-GTC, EAP-MSCHAPv2, EAP-MD5, EAP-PAX, EAP-PSK, EAP-FAST, IEEE 802.1X Supplicant, IEEE 802.1aa, EAPOL, RSN, pre-authentication, PMKSA caching, BSD WPA Authenticator, FreeBSD WPA Authenticator, RADIUS authentication server, EAP authenticator, EAP server, EAP-TNC, TNCS, IF-IMV, IF-TNCCS, WPS">
  7. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  8. </head>
  9. <body>
  10. <h2>hostapd: IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator</h2>
  11. <p>hostapd is a user space daemon for access point and authentication
  12. servers. It implements IEEE 802.11 access point management, IEEE
  13. 802.1X/WPA/WPA2/EAP Authenticators, RADIUS client, EAP server, and
  14. RADIUS authentication server. The current version supports Linux (Host
  15. AP, madwifi, mac80211-based drivers) and FreeBSD (net80211).</p>
  16. <p>hostapd is designed to be a "daemon" program that runs in the
  17. background and acts as the backend component controlling
  18. authentication. hostapd supports separate frontend programs and an
  19. example text-based frontend, hostapd_cli, is included with
  20. hostapd.</p>
  21. <h4>Supported WPA/IEEE 802.11i/EAP/IEEE 802.1X features</h4>
  22. <ul>
  23. <li>WPA-PSK ("WPA-Personal")</li>
  24. <li>WPA with EAP (with integrated EAP server or an external
  25. RADIUS backend authentication server) ("WPA-Enterprise")</li>
  26. <li>key management for CCMP, TKIP, WEP104, WEP40</li>
  27. <li>WPA and full IEEE 802.11i/RSN/WPA2</li>
  28. <li>RSN: PMKSA caching, pre-authentication</li>
  29. <li>IEEE 802.11r</li>
  30. <li>IEEE 802.11w</li>
  31. <li>RADIUS accounting</li>
  32. <li>RADIUS authentication server with EAP</li>
  33. <li>Wi-Fi Protected Setup (WPS)</li>
  34. </ul>
  35. <h4>Supported EAP methods (integrated EAP server and RADIUS authentication server)</h4>
  36. <ul>
  37. <li>EAP-TLS</li>
  38. <li>EAP-PEAP/MSCHAPv2 (both PEAPv0 and PEAPv1)</li>
  39. <li>EAP-PEAP/TLS (both PEAPv0 and PEAPv1)</li>
  40. <li>EAP-PEAP/GTC (both PEAPv0 and PEAPv1)</li>
  41. <li>EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)</li>
  42. <li>EAP-TTLS/EAP-MD5-Challenge</li>
  43. <li>EAP-TTLS/EAP-GTC</li>
  44. <li>EAP-TTLS/EAP-MSCHAPv2</li>
  45. <li>EAP-TTLS/MSCHAPv2</li>
  46. <li>EAP-TTLS/EAP-TLS</li>
  47. <li>EAP-TTLS/MSCHAP</li>
  48. <li>EAP-TTLS/PAP</li>
  49. <li>EAP-TTLS/CHAP</li>
  50. <li>EAP-SIM</li>
  51. <li>EAP-AKA</li>
  52. <li>EAP-AKA'</li>
  53. <li>EAP-PAX</li>
  54. <li>EAP-PSK</li>
  55. <li>EAP-SAKE</li>
  56. <li>EAP-FAST</li>
  57. <li>EAP-IKEv2</li>
  58. <li>EAP-GPSK</li>
  59. </ul>
  60. <p>Following methods are also supported, but since they do not generate keying
  61. material, they cannot be used with WPA or IEEE 802.1X WEP keying.</p>
  62. <ul>
  63. <li>EAP-MD5-Challenge</li>
  64. <li>EAP-MSCHAPv2</li>
  65. <li>EAP-GTC</li>
  66. <li>EAP-TNC (Trusted Network Connect; TNCS, IF-IMV, IF-T, IF-TNCCS)</li>
  67. </ul>
  68. <p>More information about EAP methods and interoperability testing is
  69. available in <a href="/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=hostapd/eap_testing.txt">eap_testing.txt</a>.</p>
  70. <h4>Supported wireless cards/drivers</h4>
  71. <ul>
  72. <li><a href="http://wireless.kernel.org/en/developers/Documentation/mac80211">Linux mac80211 drivers</a></li>
  73. <li><a href="http://w1.fi/">Host AP driver for Prism2/2.5/3</a></li>
  74. <li><a href="http://sourceforge.net/projects/madwifi/">madwifi (Atheros ar521x)</a></li>
  75. <li>BSD net80211 layer (e.g., Atheros driver) (FreeBSD 6-CURRENT)</li>
  76. </ul>
  77. <h3><a name="download">Download</a></h3>
  78. <p>
  79. <b>hostapd</b><br>
  80. Copyright (c) 2002-2009, Jouni Malinen &lt;j@w1.fi&gt;
  81. and contributors.
  82. </p>
  83. <p>
  84. This program is free software; you can redistribute it and/or modify
  85. it under the terms of the GNU General Public License version 2 as
  86. published by the Free Software Foundation. See
  87. <a href="/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=COPYING">COPYING</a>
  88. for more details.
  89. </p>
  90. <p>Alternatively, this software may be distributed, used, and modified
  91. under the terms of BSD license. See <a href="/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=hostapd/README">README</a>
  92. for more details.</p>
  93. <p>
  94. <b>Please see
  95. <a href="/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=hostapd/README">README</a>
  96. for the current documentation.</b></p>
  97. <ul>
  98. <li><a href="../releases.html">Release graph</a></li>
  99. <li>Latest stable release:
  100. <ul>
  101. <li><a href="../releases/hostapd-0.6.9.tar.gz">hostapd-0.6.9.tar.gz</a></li>
  102. </ul>
  103. <li>Latest development release:
  104. <ul>
  105. <li><a href="../releases/hostapd-0.7.0.tar.gz">hostapd-0.7.0.tar.gz</a></li>
  106. </ul>
  107. <li>ChangeLog:
  108. <ul>
  109. <li><a href="/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=hostapd/ChangeLog">development branch</a></li>
  110. <li><a href="/gitweb/gitweb.cgi?p=hostap-06.git;a=blob_plain;f=hostapd/ChangeLog">stable branch</a></li>
  111. </ul>
  112. <li><a href="../releases/">Old releases</a></li>
  113. <li><a href="http://lists.shmoo.com/mailman/listinfo/hostap">Mailing list</a></li>
  114. <li><a href="http://lists.shmoo.com/pipermail/hostap/">New mailing list archives</a></li>
  115. <li><a href="/gitweb/gitweb.cgi">Web interface to GIT repository (0.6.x and newer)</a></li>
  116. <li><a href="/cgi-bin/viewcvs.cgi/hostap/">Web interface to CVS repository (0.5.x and older)</a></li>
  117. <li><a href="../releases/snapshots/">Snapshot releases from all active branches</a>
  118. <li><a href="../cvs.html">GIT and read-only anonymous CVS access (pserver)</a></li>
  119. <li><a href="../bugz/">Bug and feature request tracking</a></li>
  120. <li><a href="../wpa_supplicant/devel/">Developers' documentation for wpa_supplicant/hostapd</a></li>
  121. </ul>
  122. <h3>WPA</h3>
  123. <p>The original security mechanism of IEEE 802.11 standard was not
  124. designed to be strong and has proven to be insufficient for most
  125. networks that require some kind of security. Task group I (Security)
  126. of <a href="http://www.ieee802.org/11/">IEEE 802.11 working group</a>
  127. has worked to address the flaws of the base standard and in
  128. practice completed its work in May 2004. The IEEE 802.11i amendment to
  129. the IEEE 802.11 standard was approved in June 2004 and published in
  130. July 2004.</p>
  131. <p><a href="http://www.wi-fi.org/">Wi-Fi Alliance</a> used a draft
  132. version of the IEEE 802.11i work (draft 3.0) to define a subset of the
  133. security enhancements that can be implemented with existing wlan
  134. hardware. This is called Wi-Fi Protected Access (WPA). This has
  135. now become a mandatory component of interoperability testing and
  136. certification done by Wi-Fi Alliance. Wi-Fi has
  137. <a href="http://www.wi-fi.org/OpenSection/protected_access.asp">information
  138. about WPA</a> at its web site.</p>
  139. <p>IEEE 802.11 standard defined wired equivalent privacy (WEP) algorithm
  140. for protecting wireless networks. WEP uses RC4 with 40-bit keys,
  141. 24-bit initialization vector (IV), and CRC32 to protect against packet
  142. forgery. All these choices have proven to be insufficient: key space is
  143. too small against current attacks, RC4 key scheduling is insufficient
  144. (beginning of the pseudorandom stream should be skipped), IV space is
  145. too small and IV reuse makes attacks easier, there is no replay
  146. protection, and non-keyed authentication does not protect against bit
  147. flipping packet data.</p>
  148. <p>WPA is an intermediate solution for the security issues. It uses
  149. Temporal Key Integrity Protocol (TKIP) to replace WEP. TKIP is a
  150. compromise on strong security and possibility to use existing
  151. hardware. It still uses RC4 for the encryption like WEP, but with
  152. per-packet RC4 keys. In addition, it implements replay protection,
  153. keyed packet authentication mechanism (Michael MIC).</p>
  154. <p>Keys can be managed using two different mechanisms. WPA can either use
  155. an external authentication server (e.g., RADIUS) and EAP just like
  156. IEEE 802.1X is using or pre-shared keys without need for additional
  157. servers. Wi-Fi calls these "WPA-Enterprise" and "WPA-Personal",
  158. respectively. Both mechanisms will generate a master session key for
  159. the Authenticator (AP) and Supplicant (client station).</p>
  160. <p>WPA implements a new key handshake (4-Way Handshake and Group Key
  161. Handshake) for generating and exchanging data encryption keys between
  162. the Authenticator and Supplicant. This handshake is also used to
  163. verify that both Authenticator and Supplicant know the master session
  164. key. These handshakes are identical regardless of the selected key
  165. management mechanism (only the method for generating master session
  166. key changes).</p>
  167. <h3>IEEE 802.11i / RSN / WPA2</h3>
  168. <p>The design for parts of IEEE 802.11i that were not included in WPA
  169. has finished (May 2004) and this amendment to IEEE 802.11 was approved
  170. in June 2004. Wi-Fi Alliance is using the final IEEE 802.11i as a new
  171. version of WPA called WPA2. This included, e.g., support for more
  172. robust encryption algorithm (CCMP: AES in Counter mode with CBC-MAC)
  173. to replace TKIP, optimizations for handoff (reduced number of messages
  174. in initial key handshake, pre-authentication, and PMKSA caching).</p>
  175. <h4>Configuration file</h4>
  176. <p>hostapd is configured using a text file that lists all the configuration
  177. parameters. See an example configuration file,
  178. <a href="/gitweb/gitweb.cgi?p=hostap.git;a=blob_plain;f=hostapd/hostapd.conf">hostapd.conf</a>,
  179. for detailed information about the configuration format and supported
  180. fields.</p>
  181. <h3>Feedback, comments, mailing list</h3>
  182. <p>
  183. Any comments, reports on success/failure, ideas for further
  184. improvement, feature requests, etc. are welcome at j@w1.fi.
  185. Please note, that I often receive more email than I have time to answer.
  186. Unfortunately, some messages may not get a reply, but I'll try to go
  187. through my mail whenever time permits.
  188. </p>
  189. <p>
  190. Host AP mailing list can also be used for topics related to
  191. hostapd. Since this list has a broader audience, your likelyhood of
  192. getting responses is higher. This list is recommended for general
  193. questions about hostapd and its development. In addition, I
  194. will send release notes to it whenever a new version is available.
  195. </p>
  196. <p>
  197. The mailing list information and web archive is at <a
  198. href="http://lists.shmoo.com/mailman/listinfo/hostap">http://lists.shmoo.com/mailman/listinfo/hostap</a>.
  199. Messages to hostap@shmoo.com will be delivered to the
  200. subscribers. Please note, that due to large number of spam and virus
  201. messages sent to the list address, the list is configured to accept
  202. messages only from subscribed addresses. Messages from unsubscribed addresses
  203. may be accepted manually, but their delivery will be delayed.
  204. </p>
  205. <p>
  206. If you want to make sure your bug report of feature request does not
  207. get lost, please report it through the bug tracking system as
  208. <a href="../bugz/enter_bug.cgi">a new
  209. bug/feature request</a>.
  210. </p>
  211. <hr>
  212. <div>
  213. <address><a href="mailto:j@w1.fi">Jouni Malinen</a></address>
  214. <!-- Created: Sun Jan 2 17:20:17 PST 2005 -->
  215. <!-- hhmts start -->
  216. Last modified: Sat Dec 12 20:45:27 EET 2009
  217. <!-- hhmts end -->
  218. </div>
  219. </body>
  220. </html>