Connection to a WPA2 Wi-Fi router fails

Hello,

This was tested on a Zynq (Cortex-A9) and a RPi4, on a 32-bit Arm 
Buildroot Linux system.

The Wi-Fi router uses WPA2 Personnal authentication.

Problem starts from buildroot releases including connman 1.45. Previous 
releases using connman 1.44 and prior are working fine. Also switching 
from 1.45 to 1.44 in a buildroot version that includes connman 1.45 works.


If a connection was previously successfully set up, for instance from 
connman 1.44 or older, `/var/log/messages` contains:

Jan  1 00:00:11 zest daemon.info connmand[141]: Adding interface wlan0 [ 
wifi ]
Jan  1 00:00:11 zest daemon.info connmand[141]: eth0 {update} flags 
36867 <UP>
Jan  1 00:00:11 zest daemon.info connmand[141]: eth0 {newlink} index 2 
address 9A:8F:85:81:67:B4 mtu 1500
Jan  1 00:00:11 zest daemon.info connmand[141]: eth0 {newlink} index 2 
operstate 2 <DOWN>
Jan  1 00:00:11 zest daemon.info dbus-daemon[120]: [system] Successfully 
activated service 'fi.w1.wpa_supplicant1'
Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {update} flags 
36931 <UP,RUNNING>
Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink} index 4 
address 8C:3D:16:20:0E:4A mtu 1500
Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink} index 4 
operstate 0 <UNKNOWN>
Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {update} flags 
36867 <UP>
Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink} index 4 
address 8C:3D:16:20:0E:4A mtu 1500
Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink} index 4 
operstate 2 <DOWN>
Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink} index 4 
address 8C:3D:16:20:0E:4A mtu 1500
Jan  1 00:00:11 zest daemon.info connmand[141]: wlan0 {newlink} index 4 
operstate 2 <DOWN>
Jan  1 00:00:11 zest daemon.info connmand[141]: Interface wlan0 [ wifi ] 
state is association
Jan  1 00:00:11 zest daemon.warn connmand[141]: Interface wlan0 [ wifi ] 
error "invalid-key"
Jan  1 00:00:11 zest daemon.info connmand[141]: Interface wlan0 [ wifi ] 
state is failure


Otherwise, when creating a new connection:

# connmanctl
Error getting VPN connections: The name net.connman.vpn was not provided 
by any .service files
connmanctl> services

connmanctl> enable wifi
Enabled wifi
connmanctl> scan wifi
Scan completed for wifi
connmanctl> services
     Kamoulox             wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk
     Livebox-D050 
wifi_8c3d16200e4a_4c697665626f782d44303530_managed_psk
     Freebox-3B4B3C 
wifi_8c3d16200e4a_46726565626f782d334234423343_managed_psk
     patetalex            wifi_8c3d16200e4a_7061746574616c6578_managed_psk
     DRAME                wifi_8c3d16200e4a_4452414d45_managed_psk
connmanctl> agent on
Agent registered
connmanctl> connect wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk
Agent RequestInput wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk
   Passphrase = [ Type=psk, Requirement=mandatory, Alternates=[ WPS ] ]
   WPS = [ Type=wpspin, Requirement=alternate ]
Passphrase? my_wifi_passphrase
Agent ReportError wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk
   invalid-key
connmanctl> Retry (yes/no)? no
Error 
/net/connman/service/wifi_8c3d16200e4a_4b616d6f756c6f78_managed_psk: 
Input/output error
connmanctl>


 From both situations it appears the wifi passphrase is not accepted.

wbx (as CC of this email) noticed that reverting commit 
5e73b55e00b97e1867397258b72f0d6e5ad7d31d allows connections to work again.

Is it a known situation? Is there a patch available?

Best,

François