P5DF081HN/T1AD2060 NXP Semiconductors, P5DF081HN/T1AD2060 Datasheet - Page 10

• Manufacturer Part Number: P5DF081HN/T1AD2060
• Description: P5DF081HN/HVQFN32/REEL13//T1AD
• Manufacturer: NXP Semiconductors
• Series: MIFARE®r

Specifications of P5DF081HN/T1AD2060

• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

NXP Semiconductors
P5DF081_SDS
Objective short data sheet
PUBLIC
8.4.4.1 Symmetric keys
8.4.4.2 Asymmetric keys
8.4.4 Key Storage (MIFARE SAM AV2 mode)
MIFARE SAM AV2 in MIFARE SAM AV2 mode can store both symmetric and asymmetric
keys.
MIFARE SAM AV2 can store up to 128 symmetric keys in up to 3 versions (only 2 versions
possible for 3TDEA keys and AES-192 keys) There only difference in the content of a key
entry compared to AV1 compatibility mode is the addition of an ExtSET byte with
extended configuration settings, as can be seen in Table 14.
Storage and configuration options:
SET configuration settings got redefined when comparing AV2 mode to the AV1
compatibility mode.
Four classes of keys are distinguished which restrict the possible usage of a key entry to
part of the SAM functionality:
Note that the key classes are mutual exclusive: one key cannot belong to more than 1 of
these classes.
KST reset when activating MIFARE SAM AV2 mode:
on, the keys stored in the KST are identified as Host, PICC, OfflineChange or
OfflineCrypto Keys. For this reason the KST is reset when activating MIFARE SAM AV2
mode, as it is not clear how to assign the existing keys to one of the classes automatically.
MIFARE SAM AV2 can store 2 RSA public key pairs and one RSA public key.MIFARE
SAM AV2 supports RSA keys with a modulus with a size from 256 bit (i.e. 32 bytes) up to
2048 bit (i.e. 256 bytes).
PKI Key Storage Table:
order to store and manage RSA asymmetric key pairs (i.e. private and public keys) and
the attributes related to keys. The PKI_KST holds 3 entries.
1. Host Keys: used for protecting the SAM-Host communication (see
2. PICC Keys: used for the card communication; depending on the key type they can be
3. OfflineChange Keys: used for some key management commands, to allow offline
4. OfflineCrypto Keys: used for offline crypto operations: e.g. for communication with the
keys are restricted to the AES key types.
used for authenticating and communicating with a MIFARE Plus, DESFire, MIFARE
Classic and/or MIFARE Ultralight C card
preparation of the cryptograms for these commands (compared to when the key
management is done with Host Keys) These keys are restricted to the AES key types.
backend or for writing encrypted data on a MIFARE Plus Slim or MIFARE Ultralight
(C) card.
All information provided in this document is subject to legal disclaimers.
Rev. 1 — 12 August 2010
MIFARE SAM AV2 uses a PKI Key Storage Table (PKI_KST) in
191710
Next to the addition of the ExtSET byte, part of the
From MIFARE SAM AV2 mode
Section
P5DF081
MIFARE SAM AV2
© NXP B.V. 2010. All rights reserved.
8.5) These
10 of 36