2024-06-20 01:16 PM - edited 2024-06-20 01:18 PM
I was trying to test the capability of the STSAFE-A110 chip to store and verify a password, but it didn't work.
StSafeA_PutAttribute() returned STSAFEA_UNSATISFIED_ACCESS_CONDITION.
StSafeA_VerifyPassword() returned STSAFEA_ENTRY_NOT_FOUND.
I'm not sure what any of this means. When I call other functions, like StSafeA_GenerateSignature() or StSafeA_VerifyMessageSignature(), they work just fine. Why would StSafeA_PutAttribute() and StSafeA_VerifyPassword() not work?
Here's my code:
char* passwordStr = "banana101"; // Same as in the OpenSSL example
int32_t statusCode;
StSafeA_VerifyPasswordBuffer_t commandResult;
// This call returns STSAFEA_UNSATISFIED_ACCESS_CONDITION instead of STSAFEA_OK
statusCode = StSafeA_PutAttribute(gStsafeHandle, STSAFEA_TAG_PASSWORD_SLOT, (uint8_t*)passwordStr, strlen(passwordStr), STSAFEA_MAC_NONE);
// This call returns STSAFEA_ENTRY_NOT_FOUND instead of STSAFEA_OK
statusCode = StSafeA_VerifyPassword(gStsafeHandle, (uint8_t*)passwordStr, &commandResult, STSAFEA_MAC_NONE);
Solved! Go to Solution.
2024-06-21 04:58 AM
Hi @Michael98006 ,
Thanks for you interest to STSAFE-A110 solution.
The password use case is only available on personalized part.
Therefore you need to contact your local ST team to make a personalization with password enabled.
You can't activate it on evaluation's part.
Best Regards,
Benjamin
2024-06-21 04:58 AM
Hi @Michael98006 ,
Thanks for you interest to STSAFE-A110 solution.
The password use case is only available on personalized part.
Therefore you need to contact your local ST team to make a personalization with password enabled.
You can't activate it on evaluation's part.
Best Regards,
Benjamin