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

Cannot enable MBEDTLS_SSL_PROTO_TLS1_3 when MBEDTLS_DYNAMIC_BUFFER=y (IDFGH-14708) #15448

Open
3 tasks done
AxelLin opened this issue Feb 22, 2025 · 1 comment
Open
3 tasks done
Assignees
Labels
Status: Opened Issue is new

Comments

@AxelLin
Copy link
Contributor

AxelLin commented Feb 22, 2025

Answers checklist.

  • I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
  • I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
  • I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Currently MBEDTLS_SSL_PROTO_TLS1_3 depends on !MBEDTLS_DYNAMIC_BUFFER.
But disabling MBEDTLS_DYNAMIC_BUFFER takes too much memory (about 20K) for ESP32.
So due to the limited memory size on esp32, it's almost not possible to support TLS1.3
for existing products using esp32.

I had asked this issue several months ago: #14126 (comment)
However, there is no update even after @AdityaHPatwardhan replied "will soon update regarding dynamic buffers with TLS 1.3". #14126 (comment) (It was 3 Months ago).

Can someone help to update the status? @mahavirj

@espressif-bot espressif-bot added the Status: Opened Issue is new label Feb 22, 2025
@github-actions github-actions bot changed the title Cannot enable MBEDTLS_SSL_PROTO_TLS1_3 when MBEDTLS_DYNAMIC_BUFFER=y Cannot enable MBEDTLS_SSL_PROTO_TLS1_3 when MBEDTLS_DYNAMIC_BUFFER=y (IDFGH-14708) Feb 22, 2025
@AdityaHPatwardhan
Copy link
Collaborator

Hi @AxelLin Thanks for raising the issue. Apologies for the delayed response on the earlier thread.
We were working on supporting other features/fixes hence could not prioritise this one. We have started working on this and @hrushikesh430 will update on this as we make progress.

@hrushikesh430 hrushikesh430 self-assigned this Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Opened Issue is new
Projects
None yet
Development

No branches or pull requests

4 participants