Environment (distro, kernel, driver, daemon):

SUSE10 ,kernel-2.6.15.3,ipw3945-1.0.3 ieee-1.1.13,ipw3945d-1.7.18
ipw3945-ucode-1.13

Problem description:set 64-bit shared key on AP , key1 1111-000-000
                                                  key2 2222-000-000
                                                  key3 3333-000-000
                                                  key4 4444-000-000
set current active key is [2] ,[3] or [4] on AP then associate to AP,the 
association would be failed. 
if you set current active key to [1] , the association can be set up, and then 
change the active key to [2],[3] or [4] the association also can be successful.

steps to reproduce:
%set current active key index to [2]
%./load debug=0x43fff
%iwconfig eth1 essid ipwdebug
%iwconfig eth1 key [2] 
%iwconfig eth1 key 2222 restricted
%iwconfig eth1 --> shows unassociate with AP 

this bug can be reproduced both on a-band and b/g band.
I have tested with linksys and netgear AP, there is the same problem.