8000 Re-examine use of `lib/mbedtls`, `lib/mbedtls_config`, `lib/mbedtls_errors` · Issue #10294 · adafruit/circuitpython · GitHub
[go: up one dir, main page]
Skip to content

Re-examine use of lib/mbedtls, lib/mbedtls_config, lib/mbedtls_errors #10294

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.

Sign up for GitHub

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

Jump to bottom
Open
dhalbert opened this issue Apr 25, 2025 · 0 comments
Open

Re-examine use of lib/mbedtls, lib/mbedtls_config, lib/mbedtls_errors #10294

dhalbert opened this issue Apr 25, 2025 · 0 comments
Labels
network
Milestone
Long term

Comments

@dhalbert
Copy link
Collaborator
dhalbert commented Apr 25, 2025 •
edited
Loading

mbedtls for CYW43 (Pico W) is provide by lib/mbedtls. For Espressif, we use the ESP-IDF component/mbedtls. But since pico-sdk 1.5.0, mbedtls is included as a submodule in pico-sdk, and an API was added.

#8926 moved ssl to shared-module, which was welcome, allowing a lot of shared code.

ESP-IDF v5.4 changed the in-flash root cert list format (see 62d16ce), which necessitated going back to ESP-IDF code for cert bundle management, instead of using the code in lib/mbedtls_config.

As the SDK's update their own use of mbedtls, version skew like this may continue to happen. Consider using the SDK-native mbedtls support in pico-sdk instead of the version copied from ESP-IDF, and using the version of mbedtls in pico-sdk to match that. A wrapper API could be developed for shared-module/ssl that has separate implementations for pico-sdk and ESP-IDF.
@dhalbert dhalbert added this to the Long term milestone Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
network
Projects
None yet
Milestone
Long term
Development

No branches or pull requests
1 participant
@dhalbert
0