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
Periodik Labs 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-PEAPv0/SIM - - - - - - - - - - + -
63
EAP-PEAPv0/AKA - - - - - - - - - - + -
64
EAP-PEAPv0/PSK - - - - - - - - - - + -
65
EAP-PEAPv0/PAX - - - - - - - - - - + -
66
EAP-PEAPv0/SAKE - - - - - - - - - - + -
67
EAP-PEAPv0/GPSK - - - - - - - - - - + -
68
EAP-PEAPv1/MSCHAPv2 - - + + + +1 + +5 +8 - + +
69
EAP-PEAPv1/GTC - - + + + +1 + +5 +8 - + +
70
EAP-PEAPv1/OTP - - - - - +1 - - - - - -
71
EAP-PEAPv1/MD5 - - - + + +1 + +5 - - + -
72
EAP-PEAPv1/TLS - - - + + +1 F +5 - - + -
73
EAP-PEAPv1/SIM - - - - - - - - - - + -
74
EAP-PEAPv1/AKA - - - - - - - - - - + -
75
EAP-PEAPv1/PSK - - - - - - - - - - + -
76
EAP-PEAPv1/PAX - - - - - - - - - - + -
77
EAP-PEAPv1/SAKE - - - - - - - - - - + -
78
EAP-PEAPv1/GPSK - - - - - - - - - - + -
79
EAP-TTLS/CHAP + - +2 + + + + + + - + -
80
EAP-TTLS/MSCHAP + - + + + + + + + - + -
81
EAP-TTLS/MSCHAPv2 + - + + + + + + + - + -
82
EAP-TTLS/PAP + - + + + + + + + - + -
83
EAP-TTLS/EAP-MD5 + - +2 + + + + + + - + -
84
EAP-TTLS/EAP-GTC + - +2 ? + + + + - - + -
85
EAP-TTLS/EAP-OTP - - - - - + - - - - - -
86
EAP-TTLS/EAP-MSCHAPv2 + - +2 + + + + + + - + -
87
EAP-TTLS/EAP-TLS + - +2 + F + + + - - + -
88
EAP-TTLS/EAP-SIM - - - - - - - - - - + -
89
EAP-TTLS/EAP-AKA - - - - - - - - - - + -
90
EAP-TTLS/EAP-PSK - - - - - - - - - - + -
91
EAP-TTLS/EAP-PAX - - - - - - - - - - + -
92
EAP-TTLS/EAP-SAKE - - - - - - - - - - + -
93
EAP-TTLS/EAP-GPSK - - - - - - - - - - + -
94
EAP-SIM + - - ? - + - ? - - + -
95
EAP-AKA - - - - - + - - - - + -
96
EAP-PSK +7 - - - - + - - - - + -
97
EAP-PAX - - - - - + - - - - + -
98
EAP-SAKE - - - - - - - - - - + -
99
EAP-GPSK - - - - - - - - - - + -
100
EAP-FAST/MSCHAPv2(prov) - - - + - - - - - + + +
101
EAP-FAST/GTC(auth) - - - + - - - - - + + +
102
EAP-FAST/MSCHAPv2(aprov)- - - - - - - - - - + +
103
EAP-FAST/GTC(aprov) - - - - - - - - - - + +
104
EAP-FAST/MD5(aprov) - - - - - - - - - - + -
105
EAP-FAST/TLS(aprov) - - - - - - - - - - + +
106
EAP-FAST/SIM(aprov) - - - - - - - - - - + -
107
EAP-FAST/AKA(aprov) - - - - - - - - - - + -
108
EAP-FAST/MSCHAPv2(auth) - - - - - - - - - - + +
109
EAP-FAST/MD5(auth) - - - - - - - - - - + -
110
EAP-FAST/TLS(auth) - - - - - - - - - - + +
111
EAP-FAST/SIM(auth) - - - - - - - - - - + -
112
EAP-FAST/AKA(auth) - - - - - - - - - - + -
113
LEAP + - + + + + F +6 - + - +
114
EAP-TNC +9 - - - - + - - - - - -
115
EAP-IKEv2 +10 - - - - - - - - - + -
117
1) PEAPv1 required new label, "client PEAP encryption" instead of "client EAP
118
encryption", during key derivation (requires phase1="peaplabel=1" in the
119
network configuration in wpa_supplicant.conf)
120
2) used FreeRADIUS as inner auth server
121
5) PEAPv1 required termination of negotiation on tunneled EAP-Success and new
122
label in key deriviation
123
(phase1="peap_outer_success=0 peaplabel=1") (in "IETF Draft 5" mode)
124
6) Authenticator simulator required patching for handling Access-Accept within
125
negotiation (for the first EAP-Success of LEAP)
126
7) tested only with an older (incompatible) draft of EAP-PSK; FreeRADIUS does
127
not support the current EAP-PSK (RFC) specification
128
8) PEAPv1 used non-standard version negotiation (client had to force v1 even
129
though server reported v0 as the highest supported version)
130
9) only EAP-TTLS/EAP-TNC tested, i.e., test did not include proper sequence of
131
client authentication followed by TNC inside the tunnel
132
10) worked only with special compatibility code to match the IKEv2 server
138
FreeRADIUS (2.0-beta/CVS snapshot)
143
- EAP-PEAPv0 / MSCHAPv2
145
- EAP-PEAPv0 / MD5-Challenge
147
- EAP-TTLS / EAP-MD5-Challenge
149
- EAP-TTLS / EAP-MSCHAPv2
154
- EAP-TTLS / MSCHAPv2
155
- EAP-TTLS / EAP-TNC (partial support; no authentication sequence)
159
Microsoft Windows Server 2003 / IAS
161
- EAP-PEAPv0 / MSCHAPv2
164
* IAS does not seem to support other EAP methods
166
Funk Odyssey 2.01.00.653
168
- EAP-PEAPv0 / MSCHAPv2
170
- EAP-PEAPv1 / MSCHAPv2
172
Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
173
- EAP-TTLS / CHAP (using FreeRADIUS as inner auth srv)
175
- EAP-TTLS / MSCHAPv2
177
- EAP-TTLS / EAP-MD5-Challenge (using FreeRADIUS as inner auth srv)
178
- EAP-TTLS / EAP-GTC (using FreeRADIUS as inner auth srv)
179
- EAP-TTLS / EAP-MSCHAPv2 (using FreeRADIUS as inner auth srv)
180
- EAP-TTLS / EAP-TLS (using FreeRADIUS as inner auth srv)
181
* not supported in Odyssey:
185
- EAP-PEAP / MD5-Challenge
188
Funk Steel-Belted Radius Enterprise Edition v4.71.739
192
- EAP-PEAPv0 / MSCHAPv2
195
- EAP-PEAPv1 / MSCHAPv2
199
Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
202
- EAP-TTLS / MSCHAPv2
204
- EAP-TTLS / EAP-MD5-Challenge
205
- EAP-TTLS / EAP-MSCHAPv2
208
Meetinghouse Aegis 1.1.4
213
- EAP-PEAPv0 / MSCHAPv2
216
- EAP-PEAPv0 / MD5-Challenge
217
- EAP-PEAPv1 / MSCHAPv2
220
- EAP-PEAPv1 / MD5-Challenge
221
Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
224
- EAP-TTLS / MSCHAPv2
226
- EAP-TTLS / EAP-MD5-Challenge
228
- EAP-TTLS / EAP-MSCHAPv2
231
(Server rejects authentication without any reason in debug log. It
232
looks like the inner TLS negotiation starts properly and the last
233
packet from Supplicant looks like the one sent in the Phase 1. The
234
server generates a valid looking reply in the same way as in Phase
235
1, but then ends up sending Access-Reject. Maybe an issue with TTLS
236
fragmentation in the Aegis server(?) The packet seems to include
237
1328 bytes of EAP-Message and this may go beyond the fragmentation
238
limit with AVP encapsulation and TLS tunneling. Note: EAP-PEAP/TLS
239
did work, so this issue seems to be with something TTLS specific.)
241
Radiator 3.17.1 (eval, with all patches up to and including 2007-05-25)
247
- EAP-PEAPv0 / MSCHAPv2
250
- EAP-PEAPv0 / MD5-Challenge
252
Note: Needed to use unknown identity in outer auth and some times the server
253
seems to get confused and fails to send proper Phase 2 data.
254
- EAP-PEAPv1 / MSCHAPv2
257
- EAP-PEAPv1 / MD5-Challenge
259
Note: This has some additional requirements for EAPTLS_MaxFragmentSize.
260
Using 1300 for outer auth and 500 for inner auth seemed to work.
261
Note: Needed to use unknown identity in outer auth and some times the server
262
seems to get confused and fails to send proper Phase 2 data.
265
- EAP-TTLS / MSCHAPv2
267
- EAP-TTLS / EAP-MD5-Challenge
270
- EAP-TTLS / EAP-MSCHAPv2
272
Note: This has some additional requirements for EAPTLS_MaxFragmentSize.
273
Using 1300 for outer auth and 500 for inner auth seemed to work.
280
Interlink Networks RAD-Series 6.1.2.7
285
- EAP-PEAPv0 / MSCHAPv2
287
- EAP-PEAPv0 / MD5-Challenge
288
- EAP-PEAPv1 / MSCHAPv2
290
- EAP-PEAPv1 / MD5-Challenge
291
Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
294
- EAP-TTLS / MSCHAPv2
296
- EAP-TTLS / EAP-MD5-Challenge
298
- EAP-TTLS / EAP-MSCHAPv2
303
(Failed to decrypt Phase 2 data)
305
Lucent NavisRadius 4.4.0
310
- EAP-PEAPv0 / MD5-Challenge
311
- EAP-PEAPv0 / MSCHAPv2
314
- EAP-PEAPv1 / MD5-Challenge
315
- EAP-PEAPv1 / MSCHAPv2
318
"IETF Draft 5" mode requires phase1="peap_outer_success=0 peaplabel=1"
319
'Cisco ACU 5.05' mode works without phase1 configuration
322
- EAP-TTLS / MSCHAPv2
324
- EAP-TTLS / EAP-MD5-Challenge
325
- EAP-TTLS / EAP-MSCHAPv2
329
Note: user certificate from NavisRadius had private key in a format
330
that wpa_supplicant could not use. Converting this to PKCS#12 and then
331
back to PEM allowed wpa_supplicant to use the key.
339
- EAP-PEAPv0 / MSCHAPv2
341
- EAP-PEAPv0 / MD5-Challenge
342
- EAP-PEAPv1 / MSCHAPv2
344
- EAP-PEAPv1 / MD5-Challenge
347
- EAP-TTLS / MSCHAPv2
349
- EAP-TTLS / EAP-MD5-Challenge
351
- EAP-TTLS / EAP-MSCHAPv2
355
Cisco Secure ACS 3.3(1) for Windows Server
356
- PEAPv1/GTC worked, but PEAPv0/GTC failed in the end after password was
357
sent successfully; ACS is replying with empty PEAP packet (TLS ACK);
358
wpa_supplicant tries to decrypt this.. Replying with TLS ACK and and
359
marking the connection completed was enough to make this work.
364
Funk Odyssey 2.01.00.653:
365
- uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
366
keys with outer EAP-Success message after this
367
- uses label "client EAP encryption"
368
- (peap_outer_success 1 and 2 work)
370
Funk Steel-Belted Radius Enterprise Edition v4.71.739
371
- uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
372
keys with outer EAP-Success message after this
373
- uses label "client EAP encryption"
374
- (peap_outer_success 1 and 2 work)
377
- uses TLV Success and Reply, sends MPPE keys with outer EAP-Success message
379
- uses label "client PEAP encryption"
381
Lucent NavisRadius 4.4.0 (in "IETF Draft 5" mode):
382
- sends tunneled EAP-Success with MPPE keys and expects the authentication to
383
terminate at this point (gets somewhat confused with reply to this)
384
- uses label "client PEAP encryption"
385
- phase1="peap_outer_success=0 peaplabel=1"
387
Lucent NavisRadius 4.4.0 (in "Cisco ACU 5.05" mode):
388
- sends tunneled EAP-Success with MPPE keys and expects to receive TLS ACK
390
- uses label "client EAP encryption"
392
Meetinghouse Aegis 1.1.4
393
- uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
394
keys with outer EAP-Success message after this
395
- uses label "client EAP encryption"
396
- peap_outer_success 1 and 2 work
added
removed
wpa_supplicant/eap_testing.txt
