aboutsummaryrefslogtreecommitdiffstats
path: root/wpa_supplicant/eap_testing.txt
blob: e1bac8ed95ddbd48d7f8336249b984cf3e64e962 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
Automatic regression and interoperability testing of wpa_supplicant's
IEEE 802.1X/EAPOL authentication

Test program:
- Linked some parts of IEEE 802.1X Authenticator implementation from
  hostapd (RADIUS client and RADIUS processing, EAP<->RADIUS
  encapsulation/decapsulation) into wpa_supplicant.
- Replaced wpa_supplicant.c and wpa.c with test code that trigger
  IEEE 802.1X authentication automatically without need for wireless
  client card or AP.
- For EAP methods that generate keying material, the key derived by the
  Supplicant is verified to match with the one received by the (now
  integrated) Authenticator.

The full automated test suite can now be run in couple of seconds, but
I'm more than willing to add new RADIUS authentication servers to make
this take a bit more time.. ;-) As an extra bonus, this can also be
seen as automatic regression/interoperability testing for the RADIUS
server, too.

In order for me to be able to use a new authentication server, the
server need to be available from Internet (at least from one static IP
address) and I will need to get suitable user name/password pairs,
certificates, and private keys for testing use. Other alternative
would be to get an evaluation version of the server so that I can
install it on my own test setup. If you are interested in providing
either server access or evaluation version, please contact me
(j@w1.fi).


Test matrix

+) tested successfully
F) failed
-) server did not support
?) not tested

Cisco ACS ----------------------------------------------------------.
hostapd --------------------------------------------------------.   |
Cisco Aironet 1200 AP (local RADIUS server) ----------------.   |   |
Periodik Labs Elektron ---------------------------------.   |   |   |
Lucent NavisRadius ---------------------------------.   |   |   |   |
Interlink RAD-Series ---------------------------.   |   |   |   |   |
Radiator -----------------------------------.   |   |   |   |   |   |
Meetinghouse Aegis ---------------------.   |   |   |   |   |   |   |
Funk Steel-Belted ------------------.   |   |   |   |   |   |   |   |
Funk Odyssey -------------------.   |   |   |   |   |   |   |   |   |
Microsoft IAS --------------.   |   |   |   |   |   |   |   |   |   |
FreeRADIUS -------------.   |   |   |   |   |   |   |   |   |   |   |
      |   |   |   |   |   |   |   |   |   |   |   |

EAP-MD5     +   -   -   +   +   +   +   +   -   -   +   +
EAP-GTC     +   -   -   ?   +   +   +   +   -   -   +   -
EAP-OTP     -   -   -   -   -   +   -   -   -   -   -   -
EAP-MSCHAPv2    +   -   -   +   +   +   +   +   -   -   +   -
EAP-TLS     +   +   +   +   +   +   +   +   -   -   +   +
EAP-PEAPv0/MSCHAPv2 +   +   +   +   +   +   +   +   +   -   +   +
EAP-PEAPv0/GTC    +   -   +   -   +   +   +   +   -   -   +   +
EAP-PEAPv0/OTP    -   -   -   -   -   +   -   -   -   -   -   -
EAP-PEAPv0/MD5    +   -   -   +   +   +   +   +   -   -   +   -
EAP-PEAPv0/TLS    +   +   -   +   +   +   F   +   -   -   +   -
EAP-PEAPv0/SIM    -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv0/AKA    -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv0/PSK    -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv0/PAX    -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv0/SAKE   -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv0/GPSK   -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv1/MSCHAPv2 -   -   +   +   +   +1  +   +5  +8  -   +   +
EAP-PEAPv1/GTC    -   -   +   +   +   +1  +   +5  +8  -   +   +
EAP-PEAPv1/OTP    -   -   -   -   -   +1  -   -   -   -   -   -
EAP-PEAPv1/MD5    -   -   -   +   +   +1  +   +5  -   -   +   -
EAP-PEAPv1/TLS    -   -   -   +   +   +1  F   +5  -   -   +   -
EAP-PEAPv1/SIM    -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv1/AKA    -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv1/PSK    -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv1/PAX    -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv1/SAKE   -   -   -   -   -   -   -   -   -   -   +   -
EAP-PEAPv1/GPSK   -   -   -   -   -   -   -   -   -   -   +   -
EAP-TTLS/CHAP   +   -   +2  +   +   +   +   +   +   -   +   -
EAP-TTLS/MSCHAP   +   -   +   +   +   +   +   +   +   -   +   -
EAP-TTLS/MSCHAPv2 +   -   +   +   +   +   +   +   +   -   +   -
EAP-TTLS/PAP    +   -   +   +   +   +   +   +   +   -   +   -
EAP-TTLS/EAP-MD5  +   -   +2  +   +   +   +   +   +   -   +   -
EAP-TTLS/EAP-GTC  +   -   +2  ?   +   +   +   +   -   -   +   -
EAP-TTLS/EAP-OTP  -   -   -   -   -   +   -   -   -   -   -   -
EAP-TTLS/EAP-MSCHAPv2 +   -   +2  +   +   +   +   +   +   -   +   -
EAP-TTLS/EAP-TLS  +   -   +2  +   F   +   +   +   -   -   +   -
EAP-TTLS/EAP-SIM  -   -   -   -   -   -   -   -   -   -   +   -
EAP-TTLS/EAP-AKA  -   -   -   -   -   -   -   -   -   -   +   -
EAP-TTLS/EAP-PSK  -   -   -   -   -   -   -   -   -   -   +   -
EAP-TTLS/EAP-PAX  -   -   -   -   -   -   -   -   -   -   +   -
EAP-TTLS/EAP-SAKE -   -   -   -   -   -   -   -   -   -   +   -
EAP-TTLS/EAP-GPSK -   -   -   -   -   -   -   -   -   -   +   -
EAP-SIM     +   -   -   ?   -   +   -   ?   -   -   +   -
EAP-AKA     -   -   -   -   -   +   -   -   -   -   +   -
EAP-PSK     +7  -   -   -   -   +   -   -   -   -   +   -
EAP-PAX     -   -   -   -   -   +   -   -   -   -   +   -
EAP-SAKE    -   -   -   -   -   -   -   -   -   -   +   -
EAP-GPSK    -   -   -   -   -   -   -   -   -   -   +   -
EAP-FAST/MSCHAPv2(prov) -   -   -   +   -   -   -   -   -   +   +   +
EAP-FAST/GTC(auth)  -   -   -   +   -   -   -   -   -   +   +   +
EAP-FAST/MSCHAPv2(aprov)-   -   -   -   -   -   -   -   -   -   +   +
EAP-FAST/GTC(aprov) -   -   -   -   -   -   -   -   -   -   +   +
EAP-FAST/TLS(aprov) -   -   -   -   -   -   -   -   -   -   +   +
EAP-FAST/SIM(aprov) -   -   -   -   -   -   -   -   -   -   +   -
EAP-FAST/AKA(aprov) -   -   -   -   -   -   -   -   -   -   +   -
EAP-FAST/MSCHAPv2(auth) -   -   -   -   -   -   -   -   -   -   +   +
EAP-FAST/TLS(auth)  -   -   -   -   -   -   -   -   -   -   +   +
EAP-FAST/SIM(auth)  -   -   -   -   -   -   -   -   -   -   +   -
EAP-FAST/AKA(auth)  -   -   -   -   -   -   -   -   -   -   +   -
LEAP      +   -   +   +   +   +   F   +6  -   +   -   +
EAP-TNC     +9  -   -   -   -   +   -   -   -   -   -   -
EAP-IKEv2   +10 -   -   -   -   -   -   -   -   -   +   -

1) PEAPv1 required new label, "client PEAP encryption" instead of "client EAP
   encryption", during key derivation (requires phase1="peaplabel=1" in the
   network configuration in wpa_supplicant.conf)
2) used FreeRADIUS as inner auth server
5) PEAPv1 required termination of negotiation on tunneled EAP-Success and new
   label in key deriviation
   (phase1="peap_outer_success=0 peaplabel=1") (in "IETF Draft 5" mode)
6) Authenticator simulator required patching for handling Access-Accept within
   negotiation (for the first EAP-Success of LEAP)
7) tested only with an older (incompatible) draft of EAP-PSK; FreeRADIUS does
   not support the current EAP-PSK (RFC) specification
8) PEAPv1 used non-standard version negotiation (client had to force v1 even
   though server reported v0 as the highest supported version)
9) only EAP-TTLS/EAP-TNC tested, i.e., test did not include proper sequence of
   client authentication followed by TNC inside the tunnel
10) worked only with special compatibility code to match the IKEv2 server
    implementation


Automated tests:

FreeRADIUS (2.0-beta/CVS snapshot)
- EAP-MD5-Challenge
- EAP-GTC
- EAP-MSCHAPv2
- EAP-TLS
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / GTC
- EAP-PEAPv0 / MD5-Challenge
- EAP-PEAPv0 / TLS
- EAP-TTLS / EAP-MD5-Challenge
- EAP-TTLS / EAP-GTC
- EAP-TTLS / EAP-MSCHAPv2
- EAP-TTLS / EAP-TLS
- EAP-TTLS / CHAP
- EAP-TTLS / PAP
- EAP-TTLS / MSCHAP
- EAP-TTLS / MSCHAPv2
- EAP-TTLS / EAP-TNC (partial support; no authentication sequence)
- EAP-SIM
- LEAP

Microsoft Windows Server 2003 / IAS
- EAP-TLS
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / TLS
- EAP-MD5
* IAS does not seem to support other EAP methods

Funk Odyssey 2.01.00.653
- EAP-TLS
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / GTC
- EAP-PEAPv1 / MSCHAPv2
- EAP-PEAPv1 / GTC
  Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
- EAP-TTLS / CHAP (using FreeRADIUS as inner auth srv)
- EAP-TTLS / MSCHAP
- EAP-TTLS / MSCHAPv2
- EAP-TTLS / PAP
- EAP-TTLS / EAP-MD5-Challenge (using FreeRADIUS as inner auth srv)
- EAP-TTLS / EAP-GTC (using FreeRADIUS as inner auth srv)
- EAP-TTLS / EAP-MSCHAPv2 (using FreeRADIUS as inner auth srv)
- EAP-TTLS / EAP-TLS (using FreeRADIUS as inner auth srv)
* not supported in Odyssey:
  - EAP-MD5-Challenge
  - EAP-GTC
  - EAP-MSCHAPv2
  - EAP-PEAP / MD5-Challenge
  - EAP-PEAP / TLS

Funk Steel-Belted Radius Enterprise Edition v4.71.739
- EAP-MD5-Challenge
- EAP-MSCHAPv2
- EAP-TLS
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / MD5
- EAP-PEAPv0 / TLS
- EAP-PEAPv1 / MSCHAPv2
- EAP-PEAPv1 / MD5
- EAP-PEAPv1 / GTC
- EAP-PEAPv1 / TLS
  Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
- EAP-TTLS / CHAP
- EAP-TTLS / MSCHAP
- EAP-TTLS / MSCHAPv2
- EAP-TTLS / PAP
- EAP-TTLS / EAP-MD5-Challenge
- EAP-TTLS / EAP-MSCHAPv2
- EAP-TTLS / EAP-TLS

Meetinghouse Aegis 1.1.4
- EAP-MD5-Challenge
- EAP-GTC
- EAP-MSCHAPv2
- EAP-TLS
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / TLS
- EAP-PEAPv0 / GTC
- EAP-PEAPv0 / MD5-Challenge
- EAP-PEAPv1 / MSCHAPv2
- EAP-PEAPv1 / TLS
- EAP-PEAPv1 / GTC
- EAP-PEAPv1 / MD5-Challenge
  Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
- EAP-TTLS / CHAP
- EAP-TTLS / MSCHAP
- EAP-TTLS / MSCHAPv2
- EAP-TTLS / PAP
- EAP-TTLS / EAP-MD5-Challenge
- EAP-TTLS / EAP-GTC
- EAP-TTLS / EAP-MSCHAPv2
* did not work
  - EAP-TTLS / EAP-TLS
    (Server rejects authentication without any reason in debug log. It
     looks like the inner TLS negotiation starts properly and the last
     packet from Supplicant looks like the one sent in the Phase 1. The
     server generates a valid looking reply in the same way as in Phase
     1, but then ends up sending Access-Reject. Maybe an issue with TTLS
     fragmentation in the Aegis server(?) The packet seems to include
     1328 bytes of EAP-Message and this may go beyond the fragmentation
     limit with AVP encapsulation and TLS tunneling. Note: EAP-PEAP/TLS
     did work, so this issue seems to be with something TTLS specific.)

Radiator 3.17.1 (eval, with all patches up to and including 2007-05-25)
- EAP-MD5-Challenge
- EAP-GTC
- EAP-OTP
- EAP-MSCHAPv2
- EAP-TLS
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / GTC
- EAP-PEAPv0 / OTP
- EAP-PEAPv0 / MD5-Challenge
- EAP-PEAPv0 / TLS
  Note: Needed to use unknown identity in outer auth and some times the server
  seems to get confused and fails to send proper Phase 2 data.
- EAP-PEAPv1 / MSCHAPv2
- EAP-PEAPv1 / GTC
- EAP-PEAPv1 / OTP
- EAP-PEAPv1 / MD5-Challenge
- EAP-PEAPv1 / TLS
  Note: This has some additional requirements for EAPTLS_MaxFragmentSize.
        Using 1300 for outer auth and 500 for inner auth seemed to work.
  Note: Needed to use unknown identity in outer auth and some times the server
  seems to get confused and fails to send proper Phase 2 data.
- EAP-TTLS / CHAP
- EAP-TTLS / MSCHAP
- EAP-TTLS / MSCHAPv2
- EAP-TTLS / PAP
- EAP-TTLS / EAP-MD5-Challenge
- EAP-TTLS / EAP-GTC
- EAP-TTLS / EAP-OTP
- EAP-TTLS / EAP-MSCHAPv2
- EAP-TTLS / EAP-TLS
  Note: This has some additional requirements for EAPTLS_MaxFragmentSize.
        Using 1300 for outer auth and 500 for inner auth seemed to work.
- EAP-SIM
- EAP-AKA
- EAP-PSK
- EAP-PAX
- EAP-TNC

Interlink Networks RAD-Series 6.1.2.7
- EAP-MD5-Challenge
- EAP-GTC
- EAP-MSCHAPv2
- EAP-TLS
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / GTC
- EAP-PEAPv0 / MD5-Challenge
- EAP-PEAPv1 / MSCHAPv2
- EAP-PEAPv1 / GTC
- EAP-PEAPv1 / MD5-Challenge
  Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption"
- EAP-TTLS / CHAP
- EAP-TTLS / MSCHAP
- EAP-TTLS / MSCHAPv2
- EAP-TTLS / PAP
- EAP-TTLS / EAP-MD5-Challenge
- EAP-TTLS / EAP-GTC
- EAP-TTLS / EAP-MSCHAPv2
- EAP-TTLS / EAP-TLS
* did not work
  - EAP-PEAPv0 / TLS
  - EAP-PEAPv1 / TLS
    (Failed to decrypt Phase 2 data)

Lucent NavisRadius 4.4.0
- EAP-MD5-Challenge
- EAP-GTC
- EAP-MSCHAPv2
- EAP-TLS
- EAP-PEAPv0 / MD5-Challenge
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / GTC
- EAP-PEAPv0 / TLS
- EAP-PEAPv1 / MD5-Challenge
- EAP-PEAPv1 / MSCHAPv2
- EAP-PEAPv1 / GTC
- EAP-PEAPv1 / TLS
  "IETF Draft 5" mode requires phase1="peap_outer_success=0 peaplabel=1"
  'Cisco ACU 5.05' mode works without phase1 configuration
- EAP-TTLS / CHAP
- EAP-TTLS / MSCHAP
- EAP-TTLS / MSCHAPv2
- EAP-TTLS / PAP
- EAP-TTLS / EAP-MD5-Challenge
- EAP-TTLS / EAP-MSCHAPv2
- EAP-TTLS / EAP-GTC
- EAP-TTLS / EAP-TLS

Note: user certificate from NavisRadius had private key in a format
that wpa_supplicant could not use. Converting this to PKCS#12 and then
back to PEM allowed wpa_supplicant to use the key.


hostapd v0.3.3
- EAP-MD5-Challenge
- EAP-GTC
- EAP-MSCHAPv2
- EAP-TLS
- EAP-PEAPv0 / MSCHAPv2
- EAP-PEAPv0 / GTC
- EAP-PEAPv0 / MD5-Challenge
- EAP-PEAPv1 / MSCHAPv2
- EAP-PEAPv1 / GTC
- EAP-PEAPv1 / MD5-Challenge
- EAP-TTLS / CHAP
- EAP-TTLS / MSCHAP
- EAP-TTLS / MSCHAPv2
- EAP-TTLS / PAP
- EAP-TTLS / EAP-MD5-Challenge
- EAP-TTLS / EAP-GTC
- EAP-TTLS / EAP-MSCHAPv2
- EAP-SIM
- EAP-PAX

Cisco Secure ACS 3.3(1) for Windows Server
- PEAPv1/GTC worked, but PEAPv0/GTC failed in the end after password was
  sent successfully; ACS is replying with empty PEAP packet (TLS ACK);
  wpa_supplicant tries to decrypt this.. Replying with TLS ACK and and
  marking the connection completed was enough to make this work.


PEAPv1:

Funk Odyssey 2.01.00.653:
- uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
  keys with outer EAP-Success message after this
- uses label "client EAP encryption"
- (peap_outer_success 1 and 2 work)

Funk Steel-Belted Radius Enterprise Edition v4.71.739
- uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
  keys with outer EAP-Success message after this
- uses label "client EAP encryption"
- (peap_outer_success 1 and 2 work)

Radiator 3.9:
- uses TLV Success and Reply, sends MPPE keys with outer EAP-Success message
  after this
- uses label "client PEAP encryption"

Lucent NavisRadius 4.4.0 (in "IETF Draft 5" mode):
- sends tunneled EAP-Success with MPPE keys and expects the authentication to
  terminate at this point (gets somewhat confused with reply to this)
- uses label "client PEAP encryption"
- phase1="peap_outer_success=0 peaplabel=1"

Lucent NavisRadius 4.4.0 (in "Cisco ACU 5.05" mode):
- sends tunneled EAP-Success with MPPE keys and expects to receive TLS ACK
  as a reply
- uses label "client EAP encryption"

Meetinghouse Aegis 1.1.4
- uses tunneled EAP-Success, expects reply in tunnel or TLS ACK, sends MPPE
  keys with outer EAP-Success message after this
- uses label "client EAP encryption"
- peap_outer_success 1 and 2 work