-
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
manifest: Update Matter SDK revision to pull new crypto changes #13540
Conversation
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. |
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 |
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. |
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
53d55d8
to
ca05581
Compare
ca05581
to
64cc882
Compare
64cc882
to
ec6d2ca
Compare
@wiba-nordic I've added some lines to the migration guide, release notes, and Matter index. We need to inform our customers that they must use PSA Crypto API to use Thread certification inheritance. In the other way, they need to build Thread libraries from sources. Could you please check the recent changes? |
doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
ec6d2ca
to
42390da
Compare
doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst
Outdated
Show resolved
Hide resolved
I am not sure what is breaking the documentation build. |
doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst
Outdated
Show resolved
Hide resolved
42390da
to
4953d80
Compare
doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left one comment to consider. I don't have very strong opinion on that and I'm not going to insist, so approving.
doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst
Outdated
Show resolved
Hide resolved
doc/nrf/releases_and_maturity/migration/migration_guide_2.6.rst
Outdated
Show resolved
Hide resolved
28d6116
to
fccd5cc
Compare
fccd5cc
to
0362789
Compare
165b004
to
4f526f0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, last round of comments from me. These are mostly minors, so approving in advance.
if (CHIP_NO_ERROR != err) { | ||
chip::Server::GetInstance().ScheduleFactoryReset(); | ||
// Return a success to not block the Matter event Loop and allow to call scheduled factory reset. | ||
err = CHIP_NO_ERROR; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it ok to return CHIP_NO_ERROR
if migration actually failed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will add documentation to the API.
d6daf62
to
cf89a1a
Compare
In this commit added a mechanism that migrates all existing operational keys from mbedTLS-related settings storage to the PSA ITS secure storage. After the migration the entries in the settings storage will not be avaliable anymore. From NCS 2.6.0 the Matter supports Arm PSA Crypto API by default, and mbedTLS is deprecated. We should not use CommonServerInitParams to initialize PSA crypto and we should do it directly in the Application instead of Chip::Server. To do it we moved PSA init and declaration from the Chip::Server to the Nordic's Matter Init. Signed-off-by: Arkadiusz Balys <[email protected]>
cf89a1a
to
7159994
Compare
In this commit added a mechanism that migrates all existing operational keys from mbedTLS-related settings storage to the PSA ITS secure storage.
After the migration the entries in the settings storage will not be avaliable anymore.