[nrf toup][crypto] Add define to enable x509 usage #679
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adigie
approved these changes
Nov 25, 2025
In some cases, we do not want to use x509 for Matter purposes, but it can be used for different use cases. In order to allow doing that and reducing the Matter footprint added the chip_crypto_use_x509 define that can control when the X509-related functions are added to the compilation. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no>
ArekBalysNordic
force-pushed
the
x509
branch
from
072ecfc to
802a766
Compare
ArekBalysNordic
force-pushed
the
x509
branch
from
802a766 to
62d12a4
Compare
ArekBalysNordic
force-pushed
the
x509
branch
from
62d12a4 to
db106c9
Compare
LuDuda
approved these changes
Nov 25, 2025
| protocol. | ||
|
|
||
| config CHIP_CRYPTO_USE_X509 | ||
| bool "MbedTLS X.509 certificate support" |
Collaborator
There was a problem hiding this comment.
Do we need to mention MbedTLS or rather say "x.509 certificate support" and instead do depends MBEDTLS or CHIP_CRYPTO_MBEDTLS (not sure which if any is correct)?
Contributor
Author
There was a problem hiding this comment.
Ok, but I will leave the default y if MBEDTLS_X509_LIBRARY instead of MBEDTLS
Added the CHIP_CRYPTO_USE_X509 kconfig option to enable or disable the x509 certificate processing for nrfconnect devices. Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no>
ArekBalysNordic
force-pushed
the
x509
branch
from
db106c9 to
73307ce
Compare
LuDuda
approved these changes
Nov 25, 2025
adigie
pushed a commit
to NordicBuilder/sdk-nrf
that referenced
this pull request
Nov 26, 2025
Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-connectedhomeip#679 Signed-off-by: Nordic Builder <pylon@nordicsemi.no>
carlescufi
pushed a commit
to nrfconnect/sdk-nrf
that referenced
this pull request
Nov 26, 2025
Automatically created by action-manifest-pr GH action from PR: nrfconnect/sdk-connectedhomeip#679 Signed-off-by: Nordic Builder <pylon@nordicsemi.no>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Added the CHIP_CRYPTO_USE_X509 kconfig option to enable or disable the x509 certificate processing for nrfconnect devices.
In some cases, we do not want to use x509 for Matter purposes, but it can be used for different use cases. In order to allow doing that and reducing the Matter footprint added the chip_crypto_use_x509 define that can control when the X509-related functions are added to the compilation.
Testing
In nrf-sdk