C.I.E – Carta di Identità Elettronica Functional Specification Version 2.0

More documents

Recommendations

Info

10.4 File IDEach file is referenced by a 2 byte identifier. In order to select unambiguously any file by itsidentifier, all files immediately under a given DF shall have different file identifiers.IDs 3F00h (Master file), 3FFFh and FFFFh are reserved by ISO.10.5 File SelectionAll file oriented commands (e.g. Read Record, Update Binary) act on the current file.After reset the MF is implicitly selected (does not need an explicit Select File command). When aDF is selected, it becomes the current DF. There is always a current DF, at all times.If an Elementary File is selected, it becomes the current EF. Not always the current EF is defined.After the selection of a DF, the current EF is undefined.If an EF with record structure is selected, then the record oriented commands (Append Record,Read Record, Update Record) may affect the current record pointer.After the EF selection, the current record pointer is undefined for linear record EF, while it points tothe newest record for cyclic record EF. Some record access mode will then affect the value of therecord pointer.Current DF and current EF are sometimes referred to as the current framework.10.6 Files usageDedicated Files are used to group related data. EF are instead used as data containers.These are the attributes of a Dedicated File:Attribute DescriptionID2-byte File IdentifierDF AID Application IDentifier, up to 16 bytesTable 4: DF attributesThese are the attributes of an Elementary File:AttributeIDFile TypeDescription2-byte File IdentifierTransparent, Linear Fixed,CIE - Functional Specification v 2.0 -Page 24/76
Linear Variable TLV or Cyclic EFSizeNet file size, without system overhead (2 bytes)Rec number number of records in a record file (max 254)Table 5: EF attributesIn addition to the listed attributes, each file has security related attributes, described later.CIE - Functional Specification v 2.0 -Page 25/76
Page 1 and 2: C.I.E. - Carta di Identità Elettro
Page 3 and 4: Table of Contents1. Revision Histor
Page 5 and 6: 12.17 GENERATE KEY PAIR ...........
Page 7 and 8: 2. IntroductionThis document is the
Page 9 and 10: 4. Reference Documents1. ISO/IEC 78
Page 11 and 12: Public Key - That key of an entity
Page 13 and 14: lsbLSBMACMFmsbMSBMSEMTSCOSOCIPINPPP
Page 15 and 16: 6. Electrical ParametersFor all ele
Page 17 and 18: 8. Answer To Reset (ATR)The Answer
Page 19 and 20: XXh XXh H5/H6 Y02h H7 Y49h H8 Y54h
Page 21 and 22: 9. Application SelectionNo explicit
Page 23: Record structure:The EF is seen at
Page 27 and 28: The card maintains an internal Secu
Page 29 and 30: BSO ID 1 01h to 1FhOPTION 1 See Tab
Page 31 and 32: RSA public key Exponent for Authent
Page 33 and 34: 11.4 Secure MessagingThe Secure Mes
Page 35 and 36: Byte Nr. SM Condition1 ENC USE IN2
Page 37 and 38: • Step 4: APDU command set up in
Page 39 and 40: 11.4.5 SM Response in SM_ENCOrigina
Page 41 and 42: 11.4.7 SM Response in SM_ENC_SIGOri
Page 43 and 44: 12. APDU ReferenceThe CIE supports
Page 45 and 46: 6A 86 Incorrect P1-P26A 87 Lc incon
Page 47 and 48: The PUT DATA - DATA_OCI acts on the
Page 49 and 50: 3DES - SM Cipher 10h 83h 03h3DES -
Page 51 and 52: 3 8Fh 6 BYTE 1: Not used - MUST be
Page 53 and 54: Table35Table 34: SELECT FILE Comman
Page 55 and 56: The operation is possible if the ac
Page 57 and 58: n has to be different from FFh.P1=0
Page 59 and 60: First and NextLast and PreviousSecu
Page 61 and 62: acktrackingallowed.b6 = 0b5 = 0b4 -
Page 63 and 64: 12.13 RESET RETRY COUNTERCLA INS P1
Page 65 and 66: 12.15 GIVE RANDOMCLA INS P1 P2 P3 D
Page 67 and 68: Security:The access condition to sa
Page 69 and 70: The access condition to satisfy is
Page 71 and 72: 0X 04 00 00 LC = 00 EmptyTable 59:
Page 73 and 74: • The length in bits of the priva
Page 75 and 76:
• a sequence of q cipher text blo
show all

C.I.E – Carta di Identità Elettronica Functional Specification Version 2.0

Create successful ePaper yourself

Delete template?

Save as template?