search

siemens / meta-iot2050

SIMATIC IOT2050 Isar/Debian Board Support Package
MIT License
130 stars 79 forks source link

Update SEBoot #313

Closed BaochengSu closed 2 years ago

BaochengSu commented 2 years ago

SEBoot is updated to D01.02.02.04 to fix:

  1. The AVS issue
  2. Some secure boot issues

Signed-off-by: Baocheng Su baocheng.su@siemens.com

jan-kiszka commented 2 years ago

Are we (or the trusted world) secured now? A more telling change log (impact of both changes) would be good.

BaochengSu commented 2 years ago

The changelog is recorded internally on our internal version control, here is only the signed artifacts.

jan-kiszka commented 2 years ago

I know, and that is exactly why I'm asking for a more details, impact oriented change log for our external users. It's time to provide that now, we have customers doing own integrations that require this.

BaochengSu commented 2 years ago

The details will be provided together with the secure boot tooling integration to this repo but now this PR.

This PR is only regarding quality issue fixing but not targeting releasing a feature to customer.

BaochengSu commented 2 years ago

The details will be provided together with the secure boot tooling integration to this repo but now this PR.

This PR is only regarding quality issue fixing but not targeting releasing a feature to customer.

In other words, this PR is only regarding quality fix that customer does not need to pay attention to.

BaochengSu commented 2 years ago

we have customers doing own integrations that require this.

Or, if I understand correctly, is there now customers already developing their security solution based on secure boot which we have not formally released?

jan-kiszka commented 2 years ago

Let's not wait until we forget to write an exhaustive changelog when tagging a release here and write proper changelogs when commiting binaries that depend on us to be commented on.

BaochengSu commented 2 years ago

There will not be changelog if there is not even version 1, such changelong related to secure boot will be reasonable only after we formally declared secure boot feature.