-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TW#26182] wifi: wpa2_enterprise with AES128-SHA cipher suite fails with HW crypto #2381
Comments
The root cause for this problem is that the crypto engine is provided with an invalid key. key_len is incorrectly hard coded to 256 bits which it's not in this case. Problem fixed by modifying fast_crypto_internal-cipher.c function fast_crypto_cipher_init as shown below:
|
Nice you probably just solved this issue too #2152 |
hi@mikaelkanstrup,thank you for your kindly remind, we have submit a merge request to fix the issue. I want to reproduce the phemenon in our site, but I can't find the openssl_cipher in my hostapd.conf, and if I add it by myself, when I run the hostapd, it reported a error which can not find the openssl_cipher choice |
@XinDeng11 The option is called 'openssl_ciphers'. I had got the name wrong in the issue description. Now edited and corrected. If still this does not work make sure you run a new enough hostapd. At least v2.4 is needed. |
Environment
git rev-parse --short HEAD
to get the commit id.): 599da58Problem Description
Connecting to wpa2_enterprise networks that selects TLS_RSA_WITH_AES_128_CBC_SHA cipher suite does not work when HW crypto/fast_crypto is used. Only software crypto works.
Expected Behavior
Actual Behavior
Steps to repropduce
Code to reproduce this issue
Use the esp-idf wpa2_enterprise example code to connect to test network
Debug Logs
Relevant ESP32 logs
Relevant hostapd logs:
The text was updated successfully, but these errors were encountered: