| Electronic Components Datasheet Search |
|
A30 Datasheet(PDF) 13 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
A30 Datasheet(HTML) 13 Page - NXP Semiconductors |
|
13 / 209 page ![]() NXP Semiconductors A30 Secure Authenticator 6.3.2 SIGMA-I authentication with ISOGeneralAuthenticate The A30 supports an asymmetric based authentication protocol. Asymmetric protocol exchanges are made via the ISOGeneralAuthenticate command outlined in Section 7.3.1. Sending the ISOGeneralAuthenticate command to initiate a SIGMA-I mutual authentication resets any ongoing mutual authentication exchange or already established secure channel session. The NTAG application must be selected before asymmetric protocol execution can commence. The Sigma-I protocol consists of an exchange of three messages between the Initiator (or SIGMA-I Verifier) and the Responder (or SIGMA-I Prover). In addition, if the certificates required are not found in the certificate cache (or if caching is not supported) then certificate request and reply messages are exchanged. The SIGMA-I protocol can be executed with the host as the initiator (or SIGMA-I Verifier) or the A30 as the initiator (with host as SIGMA-I Prover). The data format shall remain consistent no matter which role the A30 plays. If SIGMA-I Prover is used as the session protocol, then the host acts as the protocol responder. However, in this case, the host still needs to send the first command, initiating the message exchange. The access rights granted to the host are by default the rights associated with the CA root public key used to validate the host’s certificate chain. However, these rights can be reduced by the certificate issuer via a proprietary x.509 certificate extension. A certificate shall never have more access rights than its parent certificate. 6.3.2.1 Session keys As part of the protocol, both sides generate shared session keys and IV (nonce value) as follows (see Section 6.3.2.5 for session key generation details): Item Description K_e1 Encryption/Decryption key for message exchange K_m1 MAC key used to generate input for session signature IV_e1 AES CCM NONCE incremented for each message Table 6. SIGMA-I Session Keys 6.3.2.2 Message types Each SIGMA -I message has a TLV structure, where the tag indicates the type of message, and the value component is the payload. The message payload may be in plaintext, encrypted using AES-CCM, or a mixture of both, depending on the TLV tag. The following table lists the message types, corresponding tags, and session keys to be used for encryption/ decryption. Message TLV Tag Description Payload MSGI_PUBLIC_KEY A0 Initiator sends its supported AES key sizes and its ephemeral public key Protocol Options byte and Ephemeral ECDH public key (xP) in plaintext MSGI_HASH_AND_SIG A1 Initiator sends certificate hash (or full certificate) and signature Cert hash (or full certificate) and signature encrypted with <K_e1, IV_e1> MSGI_CERT_REQUEST A2 Initiator requests a certificate from responder Cert request message encrypted with <K_e1, IV_e1> Table 7. SIGMA-I Message Types A30 All information provided in this document is subject to legal disclaimers. © 2025 NXP B.V. All rights reserved. Product data sheet Rev. 3.0 — 27 January 2025 Document feedback 976730 13 / 209 |
|
Link URL |
| Does ALLDATASHEET help your business so far? [ DONATE ] |
About Alldatasheet | Advertisement | Contact us | Privacy Policy | Link to Datasheet | Link Exchange | Manufacturer List All Rights Reserved©Alldatasheet.com |
| Russian : Alldatasheetru.com | Korean : Alldatasheet.co.kr | Spanish : Alldatasheet.es | French : Alldatasheet.fr | Italian : Alldatasheetit.com Portuguese : Alldatasheetpt.com | Polish : Alldatasheet.pl | Vietnamese : Alldatasheet.vn Indian : Alldatasheet.in | Mexican : Alldatasheet.com.mx | British : Alldatasheet.co.uk | New Zealand : Alldatasheet.co.nz |
|
Family Site : ic2ic.com |
icmetro.com |