Council Regulation (EEC) No 3821/85Show full title

[F1 [F2 3.6.2.2. Command with secure messaging U.K.

This command enables the IDF to read data from the EF currently selected with secure messaging, in order to verify the integrity of the data received and to protect the confidentiality of the data in the case the EF is marked as ‘ Encrypted ’ .

[TCS_327] Command Message

Byte	Length	Value	Description
CLA	1	′0Ch′	Secure Messaging asked
INS	1	′B0h′	INS
P1	1	′XXh′	P1 (offset in bytes from the beginning of the file): Most Significant Byte
P2	1	′XXh′	P2 (offset in bytes from the beginning of the file): Least Significant Byte
Lc	1	′09h′	Length of input data for secure messaging
#6	1	′97h′	T LE : Tag for expected length specification
#7	1	′01h′	L LE : Length of expected length
#8	1	′NNh′	Expected length specification (original Le): Number of Bytes to be read
#9	1	′8Eh′	T CC : Tag for cryptographic checksum
#10	1	′04h′	L CC : Length of following cryptographic checksum
#11-#14	4	′XX..XXh′	Cryptographic checksum (4 most significant bytes)
Le	1	′00h′	As specified in ISO/IEC 7816-4

[TCS_328] Response Message if EF is not marked as ‘ Encrypted ’ and if Secure Messaging input format is correct:

Byte	Length	Value	Description
#1	1	′81h′	T PV : Tag for plain value data
#2	L	′NNh′ or ′81 NNh′	L PV : length of returned data (= original Le) L is 2 bytes if L PV >127 bytes
#(2+L)-#(1+L+NN)	NN	′XX..XXh′	Plain Data value
#(2+L+NN)	1	′8Eh′	T CC : Tag for cryptographic checksum
#(3+L+NN)	1	′04h′	L CC : Length of following cryptographic checksum
#(4+L+NN)-#(7+L+NN)	4	′XX..XXh′	Cryptographic checksum (4 most significant bytes)
SW	2	′XXXXh′	Status Words (SW1, SW2)

[TCS_329] Response Message if EF is marked as ‘ Encrypted ’ and if Secure Messaging input format is correct:

Byte	Length	Value	Description
#1	1	′87h′	T PI CG : Tag for encrypted data (cryptogram)
#2	L	′MMh′ or ′81 MMh′	L PI CG : length of returned encrypted data (different of original Le of the command due to padding) L is 2 byte if L PI CG > 127 bytes
#(2+L)-#(1+L+MM)	MM	′01XX..XXh′	Encrypted data: padding indicator and cryptogram
#(2+L+MM)	1	′8Eh′	T CC : tag for cryptographic checksum
#(3+L+MM)	1	′04h′	L CC : length of following cryptographic checksum
#(4+L+MM)-#(7+L+MM)	4	′XX..XXh′	Cryptographic checksum (4 most significant bytes)
SW	2	′XXXXh′	Status words (SW1, SW2)

The encrypted data returned contain a first byte indicating the used padding mode. For the tachograph application, the padding indicator always takes the value '01h', indicating that the used padding mode is the one specified in ISO/IEC 7816-4 (one byte with value ′80h′ followed by some null bytes: ISO/IEC 9797 method 2).

The ‘ regular ’ processing states, described for the READ BINARY command with no secure messaging (see point 3.6.2.1), can be returned using the response message structures described above, under a ′99h′ Tag (as described in TCS 335).

Additionally, some errors specifically related to secure messaging can happen. In that case, the processing state is simply returned, with no secure messaging structure involved:

[TCS_330] Response Message if incorrect Secure Messaging input format

Byte	Length	Value	Description
SW	2	′XXXXh′	Status words (SW1, SW2)

• If no current session key is available, the processing state ′6A88′ is returned. It happens either if the session key has not already been generated or if the session key validity has expired (in this case the IFD must re-run a mutual authentication process to set a new session key).

• If some expected data objects (as specified above) are missing in the secure messaging format, the processing state ′6987′ is returned: this error happens if an expected tag is missing or if the command body is not properly constructed.

• If some data objects are incorrect, the processing state returned is ′6988′: this error happens if all the required tags are present but some lengths are different from the ones expected.

• If the verification of the cryptographic checksum fails, the processing state returned is ′6688′.] ]

Textual Amendments

F1 Inserted by Council Regulation (EC) No 2135/98 of 24 September 1998 amending Regulation (EEC) No 3821/85 on recording equipment in road transport and Directive 88/599/EEC concerning the application of Regulations (EEC) No 3820/85 and (EEC) No 3821/85.

F2 Substituted by Commission Regulation (EC) No 1360/2002 of 13 June 2002 adapting for the seventh time to technical progress Council Regulation (EEC) No 3821/85 on recording equipment in road transport (Text with EEA relevance).