Problem in porting to PALM
Mon Mar 24 10:32:46 PDT 2008
On Tue, Mar 25, 2008 at 12:13:21AM +0800, Jack Yip wrote:
> I have captured the debug msg with binary packet printed out from the CISCO server.
> *Mar 8 00:24:06.587: RADSRV EAP-FAST: Add teap client 0011.d605.2cdc
> *Mar 8 00:24:06.587: RADSRV EAP-FAST: EAP-FAST pak rx:
> 01814770: 02 02000E01 616E6F6E 796D6F75 .....anonymou
> 01814780: 73 s
> *Mar 8 00:24:06.587: RADSRV EAP-FAST: EAP-FAST pak tx:
> 01851070: 0103 001A2B21 ....+!
> 01851080: 00040010 4C4F4341 4C205241 44495553 ....LOCAL RADIUS
> 01851090: 20534552 SER
Oh.. This is not ACS, but an internal EAP-FAST server in a Cisco AP..
Which version of the AP software (IOS) are you using?
> *Mar 8 00:24:06.588: RADSRV EAP-FAST: Sending TEAP start
> *Mar 8 00:24:06.731: RADSRV EAP-FAST: EAP-FAST pak rx:
> 01819650: 02 0300402B ... at +
> 01819660: 01160301 00350100 00310301 45986005 .....5...1..E.`.
> 01819670: BDA2B8BA 4D2702EA 306B7F69 80119AE7 ="8:M'.j0k.i...g
> 01819680: BD3B975E 41E59F87 E7830B97 00000A00 =;.^Ae..g.......
> 01819690: 3A003400 1B001800 1A0100 :.4........
Which TLS library (and which version of it) are you using in the client?
The ClientHello seems to advertise support for following ciphers:
> *Mar 8 00:24:06.732: RADSRV EAP-FAST: verify client_hello
> *Mar 8 00:24:06.732: RADSRV EAP-FAST: Cipher RC4_128_SHA / TLS_DH_anon_WITH_AES
> _128_CBC_SHA1 not found, client may be open source
This looks bit odd.. RC4_128_SHA is not there (which is as expected,
since this is likely for anonymous provisioning), but
TLS_DH_anon_WITH_AES_128_CBC_SHA1 is in the list.. This looks like a bug
in the authentication server. I've seen the issue before, but I've never
seen this level of debug output from the server.. Which debug options
did not enable to get this?
If I remember correctly, the server gets confused because of one of the
ciphers and refuses to do provisioning because of this. Workaround would
be to remove most of those ciphers from ClientHello and just try to use
TLS_DH_anon_WITH_AES_128_CBC_SHA which is known to not confuse the local
I don't know whether this has been fixed in a newer IOS version, but it
might be worthwhile to test upgrading if a newer firmware version is
> By the way, I should be using the wpa_supplicant-0.5.9.tar.gz for porting(not wpa_supplicant-0.5.10.tar.gz ), does it work with EAP-FAST?
Why should you use 0.5.9 instead of 0.5.10? I do not remember whether
there were any changes that could affect EAP-FAST behavior between those
versions, but in general, I would recommend using the latest available
stable version due to bug fixes included in it.
Jouni Malinen PGP id EFC895FA
More information about the Hostap