AES-CFB-128 test failed (using wpa_supplicant)

Jussi Kivilinna jussi.kivilinna at
Tue Jun 6 18:55:45 CEST 2017


On 06.06.2017 10:17, Belisko Marek wrote:
> Hi,
> I'm using wpa_supplicant v2.4 on custom x86 platform (VIA board). When
> I'm trying
> connect to AP with WPA2 and AES encryption I cannot connect due to the
> errors like (with TKIP it works fine):
> selftest for CFB failed - see syslog for details

Looks like there is wrong use of assembly operand constraints in Padlock
accelerated AES code. Can you test if the attached patch helps? Patch is
for libgcrypt-1.6.x.


> and when inspecting syslog I found :
> Libgcrypt warning: AES-CFB-128 test failed (plaintext mismatch, parallel path)
> I'm using libgcryp 1.6.3 and whole system is build using yocto.
> Compared to my laptop with same version of wpa_suplicant (v2.4) but
> libgcrypt was 1.6.5 it works fine here . Could it be some missing
> configuration or any pointer where to look? I have enabled in kernel
> config CONFIG_CRYPTO_AES_NI_INTEL=y and also
> BR,
> marek

-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix-padlock-1.patch
Type: text/x-patch
Size: 1389 bytes
Desc: not available
URL: </pipermail/attachments/20170606/fa1d9994/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 671 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20170606/fa1d9994/attachment.sig>

More information about the Gcrypt-devel mailing list