1 Automatic regression and interoperability testing of wpa_supplicant's
2 IEEE 802.1X/EAPOL authentication
5 - Linked some parts of IEEE 802.1X Authenticator implementation from
6 hostapd (RADIUS client and RADIUS processing, EAP<->RADIUS
7 encapsulation/decapsulation) into wpa_supplicant.
8 - Replaced wpa_supplicant.c and wpa.c with test code that trigger
9 IEEE 802.1X authentication automatically without need for wireless
11 - For EAP methods that generate keying material, the key derived by the
12 Supplicant is verified to match with the one received by the (now
13 integrated) Authenticator.
15 The full automated test suite can now be run in couple of seconds, but
16 I'm more than willing to add new RADIUS authentication servers to make
17 this take a bit more time.. ;-) As an extra bonus, this can also be
18 seen as automatic regression/interoperability testing for the RADIUS
21 In order for me to be able to use a new authentication server, the
22 server need to be available from Internet (at least from one static IP
23 address) and I will need to get suitable user name/password pairs,
24 certificates, and private keys for testing use. Other alternative
25 would be to get an evaluation version of the server so that I can
26 install it on my own test setup. If you are interested in providing
27 either server access or evaluation version, please contact me
33 +) tested successfully
35 -) server did not support
38 Cisco ACS ----------------------------------------------------------.
39 hostapd --------------------------------------------------------. |
40 Cisco Aironet 1200 AP (local RADIUS server) ----------------. | |
41 Corriente Elektron -------------------------------------. | | |
42 Lucent NavisRadius ---------------------------------. | | | |
43 Interlink RAD-Series ---------------------------. | | | | |
44 Radiator -----------------------------------. | | | | | |
45 Meetinghouse Aegis ---------------------. | | | | | | |
46 Funk Steel-Belted ------------------. | | | | | | | |
47 Funk Odyssey -------------------. | | | | | | | | |
48 Microsoft IAS --------------. | | | | | | | | | |
49 FreeRADIUS -------------. | | | | | | | | | | |
50 | | | | | | | | | | | |
52 EAP-MD5 + - - + + + + + - - + +
53 EAP-GTC + - - ? + + + + - - + -
54 EAP-OTP - - - - - + - - - - - -
55 EAP-MSCHAPv2 + - - + + + + + - - + -
56 EAP-TLS + + + + + + + + - - + +
57 EAP-PEAPv0/MSCHAPv2 + + + + + + + + + - + +
58 EAP-PEAPv0/GTC + - + - + + + + - - + +
59 EAP-PEAPv0/OTP - - - - - + - - - - - -
60 EAP-PEAPv0/MD5 + - - + + + + + - - + -
61 EAP-PEAPv0/TLS - + - + + + F + - - - -
62 EAP-PEAPv1/MSCHAPv2 - - + + + +1 + +5 +8 - + +
63 EAP-PEAPv1/GTC - - + + + +1 + +5 - - + +
64 EAP-PEAPv1/OTP - - - - - +1 - - - - - -
65 EAP-PEAPv1/MD5 - - - + + +1 + +5 - - + -
66 EAP-PEAPv1/TLS - - - + + +1 F +5 - - - -
67 EAP-TTLS/CHAP + - +2 + + + + + + - + -
68 EAP-TTLS/MSCHAP + - + + + + + + + - + -
69 EAP-TTLS/MSCHAPv2 + - + + + + + + + - + -
70 EAP-TTLS/PAP + - + + + + + + + - + -
71 EAP-TTLS/EAP-MD5 + - +2 + + + + + - - + -
72 EAP-TTLS/EAP-GTC + - +2 ? + + + + - - + -
73 EAP-TTLS/EAP-OTP - - - - - + - - - - - -
74 EAP-TTLS/EAP-MSCHAPv2 + - +2 + + + + + + - + -
75 EAP-TTLS/EAP-TLS - - +2 + F + + + - - - -
76 EAP-SIM +3 - - ? - + - ? - - + -
77 EAP-AKA - - - - - + - - - - - -
78 EAP-PSK +7 - - - - - - - - - + -
79 EAP-PAX - - - - - - - - - - + -
80 EAP-FAST - - - - - - - - - + - +
81 LEAP + - + + + + F +6 - + - +
83 1) PEAPv1 required new label, "client PEAP encryption" instead of "client EAP
84 encryption", during key derivation (requires phase1="peaplabel=1" in the
85 network configuration in wpa_supplicant.conf)
86 2) used FreeRADIUS as inner auth server
87 3) required a patch to FreeRADIUS to fix EAP-SIM
88 5) PEAPv1 required termination of negotiation on tunneled EAP-Success and new
89 label in key deriviation
90 (phase1="peap_outer_success=0 peaplabel=1") (in "IETF Draft 5" mode)
91 6) Authenticator simulator required patching for handling Access-Accept within
92 negotiation (for the first EAP-Success of LEAP)
93 7) EAP-PSK is not included in FreeRADIUS distribution; used external
94 rlm_eap_psk implementation from
95 http://perso.rd.francetelecom.fr/bersani/EAP_PSK/
96 EAP-PSKWindowsimplementations.html
97 8) PEAPv1 used non-standard version negotiation (client had to force v1 even
98 though server reported v0 as the highest supported version)
103 FreeRADIUS (1.0pre and CVS snapshot)
108 - EAP-PEAPv0 / MSCHAPv2
110 - EAP-PEAPv0 / MD5-Challenge
111 - EAP-TTLS / EAP-MD5-Challenge
113 - EAP-TTLS / EAP-MSCHAPv2
117 - EAP-TTLS / MSCHAPv2
119 * not supported in FreeRADIUS
120 - EAP-PEAP / TLS (Unable to tunnel TLS inside of TLS)
121 - EAP-TTLS / EAP-TLS (Unable to tunnel TLS inside of TLS)
123 Microsoft Windows Server 2003 / IAS
125 - EAP-PEAPv0 / MSCHAPv2
128 * IAS does not seem to support other EAP methods
130 Funk Odyssey 2.01.00.653
132 - EAP-PEAPv0 / MSCHAPv2
134 - EAP-PEAPv1 / MSCHAPv2
136 Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
137 - EAP-TTLS / CHAP (using FreeRADIUS as inner auth srv)
139 - EAP-TTLS / MSCHAPv2
141 - EAP-TTLS / EAP-MD5-Challenge (using FreeRADIUS as inner auth srv)
142 - EAP-TTLS / EAP-GTC (using FreeRADIUS as inner auth srv)
143 - EAP-TTLS / EAP-MSCHAPv2 (using FreeRADIUS as inner auth srv)
144 - EAP-TTLS / EAP-TLS (using FreeRADIUS as inner auth srv)
145 * not supported in Odyssey:
149 - EAP-PEAP / MD5-Challenge
152 Funk Steel-Belted Radius Enterprise Edition v4.71.739
156 - EAP-PEAPv0 / MSCHAPv2
159 - EAP-PEAPv1 / MSCHAPv2
163 Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
166 - EAP-TTLS / MSCHAPv2
168 - EAP-TTLS / EAP-MD5-Challenge
169 - EAP-TTLS / EAP-MSCHAPv2
172 Meetinghouse Aegis 1.1.4
177 - EAP-PEAPv0 / MSCHAPv2
180 - EAP-PEAPv0 / MD5-Challenge
181 - EAP-PEAPv1 / MSCHAPv2
184 - EAP-PEAPv1 / MD5-Challenge
185 Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
188 - EAP-TTLS / MSCHAPv2
190 - EAP-TTLS / EAP-MD5-Challenge
192 - EAP-TTLS / EAP-MSCHAPv2
195 (Server rejects authentication without any reason in debug log. It
196 looks like the inner TLS negotiation starts properly and the last
197 packet from Supplicant looks like the one sent in the Phase 1. The
198 server generates a valid looking reply in the same way as in Phase
199 1, but then ends up sending Access-Reject. Maybe an issue with TTLS
200 fragmentation in the Aegis server(?) The packet seems to include
201 1328 bytes of EAP-Message and this may go beyond the fragmentation
202 limit with AVP encapsulation and TLS tunneling. Note: EAP-PEAP/TLS
203 did work, so this issue seems to be with something TTLS specific.)
205 Radiator 3.9 (eval, with all patches up to and including 2004-08-30)
211 - EAP-PEAPv0 / MSCHAPv2
214 - EAP-PEAPv0 / MD5-Challenge
216 Note: Needed to use unknown identity in outer auth and some times the server
217 seems to get confused and fails to send proper Phase 2 data.
218 - EAP-PEAPv1 / MSCHAPv2
221 - EAP-PEAPv1 / MD5-Challenge
223 Note: This has some additional requirements for EAPTLS_MaxFragmentSize.
224 Using 1300 for outer auth and 500 for inner auth seemed to work.
225 Note: Needed to use unknown identity in outer auth and some times the server
226 seems to get confused and fails to send proper Phase 2 data.
229 - EAP-TTLS / MSCHAPv2
231 - EAP-TTLS / EAP-MD5-Challenge
234 - EAP-TTLS / EAP-MSCHAPv2
236 Note: This has some additional requirements for EAPTLS_MaxFragmentSize.
237 Using 1300 for outer auth and 500 for inner auth seemed to work.
241 Interlink Networks RAD-Series 6.1.2.7
246 - EAP-PEAPv0 / MSCHAPv2
248 - EAP-PEAPv0 / MD5-Challenge
249 - EAP-PEAPv1 / MSCHAPv2
251 - EAP-PEAPv1 / MD5-Challenge
252 Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
255 - EAP-TTLS / MSCHAPv2
257 - EAP-TTLS / EAP-MD5-Challenge
259 - EAP-TTLS / EAP-MSCHAPv2
264 (Failed to decrypt Phase 2 data)
266 Lucent NavisRadius 4.4.0
271 - EAP-PEAPv0 / MD5-Challenge
272 - EAP-PEAPv0 / MSCHAPv2
275 - EAP-PEAPv1 / MD5-Challenge
276 - EAP-PEAPv1 / MSCHAPv2
279 "IETF Draft 5" mode requires phase1="peap_outer_success=0 peaplabel=1"
280 'Cisco ACU 5.05' mode works without phase1 configuration
283 - EAP-TTLS / MSCHAPv2
285 - EAP-TTLS / EAP-MD5-Challenge
286 - EAP-TTLS / EAP-MSCHAPv2
290 Note: user certificate from NavisRadius had private key in a format
291 that wpa_supplicant could not use. Converting this to PKCS#12 and then
292 back to PEM allowed wpa_supplicant to use the key.
300 - EAP-PEAPv0 / MSCHAPv2
302 - EAP-PEAPv0 / MD5-Challenge
303 - EAP-PEAPv1 / MSCHAPv2
305 - EAP-PEAPv1 / MD5-Challenge
308 - EAP-TTLS / MSCHAPv2
310 - EAP-TTLS / EAP-MD5-Challenge
312 - EAP-TTLS / EAP-MSCHAPv2
316 Cisco Secure ACS 3.3(1) for Windows Server
317 - PEAPv1/GTC worked, but PEAPv0/GTC failed in the end after password was
318 sent successfully; ACS is replying with empty PEAP packet (TLS ACK);
319 wpa_supplicant tries to decrypt this.. Replying with TLS ACK and and
320 marking the connection completed was enough to make this work.
325 Funk Odyssey 2.01.00.653:
326 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
327 keys with outer EAP-Success message after this
328 - uses label "client EAP encryption"
329 - (peap_outer_success 1 and 2 work)
331 Funk Steel-Belted Radius Enterprise Edition v4.71.739
332 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
333 keys with outer EAP-Success message after this
334 - uses label "client EAP encryption"
335 - (peap_outer_success 1 and 2 work)
338 - uses TLV Success and Reply, sends MPPE keys with outer EAP-Success message
340 - uses label "client PEAP encryption"
342 Lucent NavisRadius 4.4.0 (in "IETF Draft 5" mode):
343 - sends tunneled EAP-Success with MPPE keys and expects the authentication to
344 terminate at this point (gets somewhat confused with reply to this)
345 - uses label "client PEAP encryption"
346 - phase1="peap_outer_success=0 peaplabel=1"
348 Lucent NavisRadius 4.4.0 (in "Cisco ACU 5.05" mode):
349 - sends tunneled EAP-Success with MPPE keys and expects to receive TLS ACK
351 - uses label "client EAP encryption"
353 Meetinghouse Aegis 1.1.4
354 - uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
355 keys with outer EAP-Success message after this
356 - uses label "client EAP encryption"
357 - peap_outer_success 1 and 2 work