-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
nrf_security: kconfig: Dont enable TLS or X509 by default #14487
nrf_security: kconfig: Dont enable TLS or X509 by default #14487
Conversation
Test specificationCI/Jenkins/NRF
CI/Jenkins/integration
test-fw-nrfconnect-chip: added because there was no .github/test-spec.yml in 'matter' Detailed information of selected test modules Note: This message is automatically posted and updated by the CI |
6cb6766
to
4afd2f2
Compare
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
4afd2f2
to
cc79797
Compare
The following west manifest projects have been modified in this Pull Request:
Note: This message is automatically posted and updated by the Manifest GitHub Action. |
cc79797
to
2d004a7
Compare
2d004a7
to
ba2a21f
Compare
update matter Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
It is bad practice for features to be enabled by default. It is not clear to me why these should be enabled when PSA and legacy ECD* are enabled. Enable PK_PARSE_C explicitly (used by hostap/src/crypto/crypto_mbedtls-ec.c) now that legacy is disabled by default. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
ba2a21f
to
a2b23a8
Compare
I'm giving up on this. I expect this to change significantly soon anyway. |
It is bad practice for features to be enabled by default.
It is not clear to me why these should be enabled when PSA and legacy ECD* are enabled.