Secure AuthenticationのトピックConnection Authentication, AES 32 byte key

Connection Authentication, AES 32 byte key

deang — Sat, 26 Sep 2020 22:19:01 GMT

Can you authenticate with a 32 byte AES key vs. 16 byte key? I am able to connect using kSSS_AuthType_AESKey OK when the key is 16 bytes, fails when I try a 32 byte key.

Thanks,

Dean G.

Re: Connection Authentication, AES 32 byte key

Kan_Li — Wed, 30 Sep 2020 09:30:14 GMT

Hi @deang ,

Did you build the application based on the MW? Is it possible to share part of your code for Connection Authentication? We may try to reproduce this issue here.

Thanks for your patience!

Have a great day,
Kan

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!
- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: Connection Authentication, AES 32 byte key

deang — Wed, 30 Sep 2020 19:52:44 GMT

Hi Kan,

Yes I am using the MW. The attached source file (Test_SE_project.c) contains my test code. Ignore all of the other test code, the init_se050() function is where authentication is failing when using 256 AES key vs. 128. Use the SE_AUTH_AES authentication type, the keys are set in create_aes_authkey(), the aes_auth_key is used. If I set to 32 bytes it fails.

Dean

Re: Connection Authentication, AES 32 byte key

deang — Thu, 01 Oct 2020 21:58:13 GMT

Digging further, the SCP03 protocol spec from GlobalPlatform, Card spec V2.3, Amendment D Versin 1.1.2 March 2019 (Document GPC_SPE_014) does allow for 32 byte keys. But this is the official spec, what is actually supported by NXP is "implementation specific". So while the spec says Yes 32 byte keys allowed, NXP just didn't implement it. That's my guess.