hostapd / ath9k 4-way handshake fail (solved)

Hector Akamine hectoraka at gmail.com
Thu Jul 16 00:45:01 EDT 2009


Hello,

> Are the hostapd and wpa_supplicant running on similar CPUs and with
> similar build tools/configuration? This looks like a bug somewhere and
> should not really happen if everything works correctly.
> 

It seems that the problem was that I commented out too many lines in the
 hostapd .config file.

> > SSID - hexdump_ascii(len=16):
> >      68 6f 73 74 61 70 64 41 50 2d 73 74 61 30 30 31   hostapdAP-sta001
> > PSK (ASCII passphrase) - hexdump_ascii(len=10):
> >      73 74 61 30 30 31 70 61 73 73                     sta001pass      
> > PSK (from passphrase) - hexdump(len=32): 18 40 0d 03 5a e6 b7 db b0 bf ca cd 
> > b9 de 38 59 ba 9f d0 99 2d 35 6e a6 73 3b f0 e2 26 2e 8e 18
> 
> This PSK is incorrect.

The .config file that I used to compile this problematic hostapd was only:

CONFIG_DRIVER_NL80211=y
CONFIG_IEEE80211N=y

While using the above .config I had some warnings while compiling:

-----
cc -MMD -O2 -Wall -g -DHOSTAPD_DUMP_STATE -I../src -I../src/crypto
-I../src/utils -I../src/common -DCONFIG_CTRL_IFACE -DCONFIG_CTRL_IFACE_UNIX
-DCONFIG_IEEE80211N -DCONFIG_DRIVER_NL80211 -DINTERNAL_AES -DINTERNAL_SHA1
-DINTERNAL_SHA256 -DINTERNAL_MD5 -DCONFIG_NO_FIPS186_2_PRF -DCONFIG_NO_T_PRF
-DCONFIG_NO_TLS_PRF   -c -o ../src/crypto/sha1.o ../src/crypto/sha1.c
../src/crypto/sha1.c: In function ‘SHA1Transform’:
../src/crypto/sha1.c:641: warning: dereferencing pointer ‘block’ does break
strict-aliasing rules
(this warning repeated several times)
-----


I recompiled again with the following .config and it was ok (PSK was 
correctly computed and the warnings dissappeared)
 
CONFIG_DRIVER_NL80211=y
CONFIG_EAP=y
CONFIG_EAP_MD5=y
CONFIG_EAP_TLS=y
CONFIG_EAP_MSCHAPV2=y
CONFIG_EAP_PEAP=y
CONFIG_EAP_GTC=y
CONFIG_EAP_TTLS=y
CONFIG_PKCS12=y
CONFIG_IPV6=y
CONFIG_IEEE80211N=y


I'm not sure but I guess the problem was the missing CONFIG_EAP=y (I thought 
I needed only for WPA enterprise, not for WPA-PSK)


Best regards,
Hector



More information about the HostAP mailing list