Skip to content
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

ESP32 wpa_supplicant does not accept sha384-signed certificates (IDFGH-5756) #7465

Closed
redfast00 opened this issue Aug 24, 2021 · 2 comments
Closed
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally

Comments

@redfast00
Copy link
Contributor

My university recently switched their certificates for eduroam (a WPA enterprise network), causing all ESP-type microcontrollers not to be able to connect to the network anymore (even if they don't validate certificates). I disabled mbed-tls in wpa_supplicant and used the built-in tls library (this is easier to debug). The issue is here https://github.com/espressif/esp-idf/blob/master/components/wpa_supplicant/src/tls/x509v3.c#L1630. I "fixed" this by adding return 0;, but this can probably be properly fixed with https://patchwork.ozlabs.org/project/hostap/patch/1448154178-17670-5-git-send-email-pali.rohar@gmail.com/. There's also a bug with negotiating this certificate with mbed-tls, but this was harder to find so I didn't do that.

Environment

  • Development Kit: ESP32-S2-Saola
  • IDF version (run git describe --tags to find it): v4.3
  • Build System: idf.py
  • Compiler version (run xtensa-esp32-elf-gcc --version to find it):
  • Operating System: Linux
  • Using an IDE?: No
  • Power Supply: USB
@espressif-bot espressif-bot added the Status: Opened Issue is new label Aug 24, 2021
@github-actions github-actions bot changed the title ESP32 wpa_supplicant does not accept sha384-signed certificates ESP32 wpa_supplicant does not accept sha384-signed certificates (IDFGH-5756) Aug 24, 2021
@kapilkedawat
Copy link
Collaborator

Hi @redfast00 , can you please provide following info.

  1. Supplicant and mbedTLS logs(You can go to their respective configuration in components in menuconfig and enable those)
  2. Sniffer capture during the connection.
  3. Certificates.
  4. If certificate sharing is not possible, key size used in certificates.

Thanks

@espressif-bot espressif-bot added Resolution: NA Issue resolution is unavailable Status: Done Issue is done internally Resolution: Done Issue is done internally and removed Status: Opened Issue is new Resolution: NA Issue resolution is unavailable labels Sep 13, 2021
@AxelLin
Copy link
Contributor

AxelLin commented Oct 14, 2021

Just to remind this fix needs to backport for stable branches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Done Issue is done internally Status: Done Issue is done internally
Projects
None yet
Development

No branches or pull requests

4 participants