| Electronic Components Datasheet Search |
|
A30 Datasheet(PDF) 88 Page - NXP Semiconductors |
|
|
|||||||||||||||||||||||||||||
A30 Datasheet(HTML) 88 Page - NXP Semiconductors |
|
88 / 209 page ![]() NXP Semiconductors A30 Secure Authenticator The subject contains a subset of GetVersion: VendorID || HWMajorVersion || HWMinorVersion || SWType || SWSubType || SWMajorVersion || SWMinorVersion. This is encoded in a description (OID 2.5.4.13)[29], using hexadecimal ASCII encoding. 6.16.1.3 Card-unilateral authentication The authentication supported by Priv.Orig is outlined in Section 6.3.3. 6.16.2 Application Key Pair and Certificate At application-level, in the default configuration, A30 is trust-provisioned during manufacturing with an App- level key pair (Priv.App, Pub.App) and related certificate Cert.App. This can be used to authenticate individual devices for executing App-level functionality. 6.16.2.1 Application Key Pair The application key pair (Priv.App, Pub.App) is a unique key pair per die from which the Priv.App is stored as ECCPrivateKey KeyNo 0x00 within the application, holding with following default configuration: • NIST P-256 • KeyPolicy: 0x0004, only allowing SIGMA-I Mutual Authentication. Note that by default both Prover and Verifier mode are enabled. For privacy (non-traceability), only Prover may be preferred, with requires configuration per interface (I2C) via SetConfiguration Option 0x0F/0x10. • WriteAccess: 0x30, allowing replacement with ManageKeyPair after an authentication granting AppMasterKey access rights in CommMode.Full. • KUCLimit: disabled. For KeyPolicy and WriteAccess encoding, refer also to ManageKeyPair API definition. Pub.App is trusted via the certificate Cert.App, as specified in the next subsection. 6.16.2.2 Application Certificate The Cert.App is stored as an uncompressed end-leaf certificate without parent certificates within a certificate repository, seeSection 6.8.1, with id 0x00, with following default configuration: • Associated with the ECCPrivateKey with KeyNo 0x00. • Repository size: [TBD] • WriteAccess: 0x30, allowing ManageCertRepo after an authentication granting AppMasterKey access rights in CommMode.Full. • ReadAccess: 0x30, allowing ReadCertRepo after an authentication granting AppMasterKey access rights in CommMode.Full. Note that typically the certificate is only to be retrieved via the SIGMA-I authentication itself. Though if needed this configuration can be changed, requiring the certificate to be re-loaded. • No mapping table, this means the certificate is stored as a plain X.509 certificate without any PKCS#7 wrapping. The certificate repository is already activated and thus ready for use with the SIGMA-I authentication. The Cert.App is signed by NXP Trust Provisioning using a dedicated key pair. The CA key pair can be retrieved from https://www.gp-ca.nxp.com/CA/getCA?caid=63709320101003 filling in the CAID with the serialNumber encoded in the issuer name. The Cert.App is a public-key certificate according to X.509 v3 format [11]. It has the same structure as the Cert.Orig defined in subsection 17.1.2 with the following content. 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 88 / 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 |