[Microchip TA-100] Fix port + update to cryptoauthlib v3.6.0#9702
[Microchip TA-100] Fix port + update to cryptoauthlib v3.6.0#9702danielinux wants to merge 14 commits intowolfSSL:masterfrom
Conversation
03c4ab8 to
199c152
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 19 out of 19 changed files in this pull request and generated 11 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Jenkins retest this please. |
f6c5f77 to
81086ff
Compare
|
Jenkins retest this please |
|
@danielinux Please rebase and squash this. Hopefully that will resolve things. |
81086ff to
36b0e21
Compare
|
@tmael can you please help get this PR rebased, merge conflicts resolved and ready for merge? This work has been lingering for way too long. |
wolfcrypt/test/test.c
Outdated
| if (ret) { | ||
| goto exit_rsa; | ||
| } | ||
| ret = wc_RsaPublicEncrypt(in, inLen, out, 256, key, &rng); |
There was a problem hiding this comment.
Let's not duplicate these lines. Just make sure outSz = 256 and use the single call below.
|
Jenkins retest this please |
|
@tmael please change build errors. Might just need to rebase and force push. |
| byte keyIdSet; | ||
| #endif | ||
| #if defined(WOLFSSL_MICROCHIP_TA100) | ||
| uint16_t rKeyH; /* private key handle */ |
There was a problem hiding this comment.
uint16_t is fine since it matches what is in cryptauthlib
| plain = NULL; | ||
| TEST_SLEEP(); | ||
|
|
||
| #if defined(WOLFSSL_MICROCHIP_TA100) |
There was a problem hiding this comment.
Should this flow be used for all cases (not just TA100)? Or maybe its good to test both API methods in non TA100 case?
There was a problem hiding this comment.
I’m unsure and don’t want to introduce any side effects for non-TA100 tests.
| ERROR_OUT(WC_TEST_RET_ENC_EC(ret), exit_rsa); | ||
| #endif | ||
|
|
||
| #if defined(WOLFSSL_KEY_GEN) && defined(WOLFSSL_MICROCHIP_TA100) |
There was a problem hiding this comment.
Again couldn't this be useful in other non TA-100 cases too?
There was a problem hiding this comment.
Not useful. Non-TA100 use cases already use keys from a buffer, and we have key generation tests in other areas.
- Using correct slot ID for AES keys - Adjust IV length - Fallback operations to software for unsupported ECC curves (all tests passing)
ECC384 should be supported in TA-100
…e AS_IF to conditionally run the manual search fallback
…kg.m4 is unavailable
…#ifndef WOLFSSL_MICROCHIP_TA100
Description
Rework of TA-100 support to match cryptoauthlib v3.6.0's API. AES-GCM now working.
Fixes zd#20640
Testing
Used wolfDemo board (STM32U585) + TA100 mikrobus module.
Test log (with verbose TA-100 interactions) attached.
test_12a16e6cc.log