Good morning,
I am Paul Goulpié, technical expert at Smile ECS - integrator of open source embedded solutions.
I am contacting you because I have some questions related to the secure boot solution (mcuboot).
I am using the following evaluation board: B-U585I-IOT02A.
I am using the following reference project: https://github.com/STMicroelectronics/STM32CubeU5/tree/main/Projects/B-U585I-IOT02A/Applications/SBSFU
Currently I see that the key format used to create the signature is RSA2048. I would have liked to use an RSA4096 key.
Can you tell me if there is a hardware restriction that would prevent it from being used. I am well aware that software modifications at different levels are necessary, however I would have liked to know in advance if a blockage on the hard side (bootRomCode or other) prevents this implementation from being carried out.
Are you aware of the completion of this integration (on an internal or external project).
On a similar project I have the signing step which is outsourced (via a PKI, which supports the signing of a binary). Do you have a description of a workflow that implements this outsourced signature step?
Thanking you in advance for your responses.
Kind regards,
Paul Goulpie
