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

CA callback not called in TLS 1.3 #7079

Closed
gilles-peskine-arm opened this issue Feb 10, 2023 · 4 comments
Closed

CA callback not called in TLS 1.3 #7079

gilles-peskine-arm opened this issue Feb 10, 2023 · 4 comments
Assignees
Labels
bug component-tls13 size-s Estimated task size: small (~2d)

Comments

@gilles-peskine-arm
Copy link
Contributor

gilles-peskine-arm commented Feb 10, 2023

Configuring a CA callback with mbedtls_ssl_conf_ca_cb() has no effect in TLS 1.3. This is not documented as a limitation, and there is no reason not to support it. See #7075 (comment)

The goal of this task is to support a CA callback in TLS 1.3, the same way as in TLS 1.2.

This should be tested both from the server side and the client side.

@gilles-peskine-arm
Copy link
Contributor Author

Related: TLS currently doesn't support the X.509 certificate extension callback (only available via mbedtls_x509_crt_parse_der_with_ext_cb). Whatever method we add to make it support this, should work both for TLS 1.2 and TLS 1.3.

@adambvidex
Copy link

Is there a workaround for this bug? Our product requires it because the CA database cannot fit in RAM of the embedded device.

@ronald-cron-arm
Copy link
Contributor

Is there a workaround for this bug? Our product requires it because the CA database cannot fit in RAM of the embedded device.

#9002 fixes this issue.

@ronald-cron-arm
Copy link
Contributor

Closing this issue as we have rather decided to address this more generally with #9018.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug component-tls13 size-s Estimated task size: small (~2d)
Projects
Status: 3.6.1 patch release
Development

Successfully merging a pull request may close this issue.

3 participants