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

wolfssl: fix CA certificate multiple location import #16391

Closed
wants to merge 1 commit into from

Conversation

jay
Copy link
Member

@jay jay commented Feb 19, 2025

  • Do not set x509_store_setup until after all CA certificate imports.

  • If CA blob import fails then return error unconditionally.

This is to sync the behavior with OpenSSL and other backends.

Prior to this change, setting CA native and/or CA blob were treated as mutually exclusive from setting CA file and/or CA path.

CA blob import still overrides CA file import as documented.

Closes #xxxx

- Do not set x509_store_setup until after all CA certificate imports.

- If CA blob import fails then return error unconditionally.

This is to sync the behavior with OpenSSL and other backends.

Prior to this change, setting CA native and/or CA blob were treated as
mutually exclusive from setting CA file and/or CA path.

CA blob import still overrides CA file import as documented.

Closes #xxxx
@jay jay added the TLS label Feb 19, 2025
@jay
Copy link
Member Author

jay commented Feb 19, 2025

I notice wolfSSL can only set ca-native if WOLFSSL_SYS_CA_CERTS is defined, I wonder how common that type of build is in wolfSSL land, perhaps we should warn if ca-native is ignored due to missing WOLFSSL_SYS_CA_CERTS?

edit: I will address this separately

@jay jay closed this in 210c0c0 Feb 21, 2025
@jay jay deleted the wolfssl_multiple_ca branch February 21, 2025 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

1 participant