search

Samsung / TizenRT

TizenRT is a lightweight RTOS-based platform to support low-end IoT devices
Apache License 2.0
561 stars 560 forks source link

os/se/ameba: SE Support GCM mode #6267

Open ZhenBei-Sin opened 1 week ago

ZhenBei-Sin commented 1 week ago

Change Notes:

ZhenBei-Sin commented 1 week ago

Hi @sunghan-chang & @jylee9613

The GCM mode was ready. Please help to verify. For the TP1x: PR was submitted for the SE lib with included the GCM mode. Please re-gen the KM4 img3 from the PR and commit to TizenRT.

Thank You.

Best Regards, Zhen Bei

sunghan-chang commented 1 week ago

@ZhenBei-Sin How about separating the pr for implement secure reboot reason?

ZhenBei-Sin commented 1 week ago

@ZhenBei-Sin How about separating the pr for implement secure reboot reason?

FYI: The changes was affected the secure BL image. So put under same PR with separate commit. If require to separate PR, it will do it…

Thank you.

ZhenBei-Sin commented 5 days ago

@ZhenBei-Sin How about separating the pr for implement secure reboot reason?

FYI: The changes was affected the secure BL image. So put under same PR with separate commit. If require to separate PR, it will do it…

Thank you.

Hi @sunghan-chang Could you let me know, still want to remain or separate PR? Thank You.

sunghan-chang commented 5 days ago

@ZhenBei-Sin GCM could be merged atleast 1 and half week later. How about merging the reboot reason first?

ZhenBei-Sin commented 4 days ago

@ZhenBei-Sin GCM could be merged atleast 1 and half week later. How about merging the reboot reason first?

Hi @sunghan-chang The reboot reason is for the secure part and the implementation is secure. I will proceed to separate the PR.

  1. With implementation secure reboot reason.
  2. GCM. (will include the 1. changes in SE)

Any concern ?

sunghan-chang commented 4 days ago

@ZhenBei-Sin GCM could be merged atleast 1 and half week later. How about merging the reboot reason first?

Hi @sunghan-chang The reboot reason is for the secure part and the implementation is secure. I will proceed to separate the PR.

  1. With implementation secure reboot reason.
  2. GCM. (will include the 1. changes in SE)

Any concern ?

It looks ok.

ZhenBei-Sin commented 4 days ago

@ZhenBei-Sin GCM could be merged atleast 1 and half week later. How about merging the reboot reason first?

Hi @sunghan-chang The reboot reason is for the secure part and the implementation is secure. I will proceed to separate the PR.

  1. With implementation secure reboot reason.
  2. GCM. (will include the 1. changes in SE)

Any concern ?

It looks ok.

Done separate the PR. PR#6274.

sunghan-chang commented 4 days ago

NOTE!! This must be merged after PR #6274 .