Daniele Lacamera

I'm closing this in favor of #441 (if I understand correctly this was initially handled in #427). Feel free to continue the discussion there.

Suggesting to add `WOLFSSL_NO_HASH_RAW` to the build with DCP. Closing this PR.

Hi @opkaizen, thanks for spotting this. Could you please get in touch with [email protected] to set up a contributor agreement?

hi @opkaizen did you get in touch with us yet regarding the CA?

@dgarske this is now working properly with Trustzone-M + secure wolfCrypt + PKCS11 app, and it is ready for review.

Hi @kojo1 what is the status on this one? We have recently received some enquiry about this port.

Hey @UffTechn , Thanks for reporting this. Your approach seems valid. The `fork_bootloader()` should do nothing if the contents already match. Which means it should only run once after the...

@UffTechn I changed the fork_bootloader call so that it returns immediately if the content in the second bank already matches. Please confirm this would solve your case, and regardless whether...

Thanks for confirming! Closing this issue.

Hello @bolons Thank you for testing our IoT-Safe module. The current implementation indeed only supports SHA256, as we had not tested the code against an applet supporting different hash sizes....