Start Send File to Device (Secured) - Command 0xD811
The host uses this command to start sending secured files to the device for storage or processing. It is similar to Start Send File to Device (Unsecured) - Command 0xD812, but is used to send a different subset of file types that impact device security and require some form of authentication from the host. Refer to Table 206 to determine which file type requires a secure command. All files require the command to be authorized via a secure wrapper. In some cases, files include additional signatures within the file structure itself. This command is paired with Start Get File from Device - Command 0xD821, which the host can use to retrieve files. However, some file types are “one way only” and cannot be retrieved using that command after the host sends them to the device.
Sequence of Events — Step 4
The host constructs Send Secured Command to Device - Command 0xEEEE using the previously constructed command as the payload, and sends that command to the device as a Request Message to start the process of uploading a file.
Sub-steps and notes for building the secured wrapper:
Use Get Key Info - Command 0xEF11 to gather information about the key to use to secure the message payload(s). Because this command requires a MAC, use key slot 1111.
Build the Security Parameters Type portion of the wrapper with:
Security Operation Type populated with the following values:
Operation Type = Command Authorization Using MAC
Operation Algorithm = CMAC
Operation Cipher = AES-256
Padding = One and zeros
MAC Block Size with any number
Key Information Type populated with the key information gathered earlier.
Table SFDS-1 - Request Data for Start Send File to Device (Secured) - Command 0xD811
Beginning of any wrappers, at minimum including Request Message
D811 = Start Send File to Device (Secured) - Command 0xD811
81
04
File ID from Table 206
B
R
A2
var
File transfer properties
T
R
/81
Var
Length of File Payload
This is the length of the File Payload parameter in the Data File Message the host sends to the device.
B
R
/82
01
Hash Checksum Type
0x04 = SHA-256
B
R
/83
20
Hash Checksum Anticipated checksum calculated against the File Payload, according to the standard specified in Hash Checksum Type.
B
R
A3
var
File Description The host should populate this value to help identify the file using Get File Info from Device. - Command 0xD825
T
R
/81
var
File Name Maximum length 32 bytes Reserved for future use. Leave empty.
B
O
Null
/82
var
File Label Maximum length 16 bytes Reserved for future use. Leave empty.
B
O
Null
/83
var
File Version Maximum length 7 bytes Reserved for future use. Leave empty.
B
O
Null
/84
var
File Date Maximum length 20 bytes Reserved for future use. Leave empty.
B
O
Null
87
01
Reserved for future use. Leave empty.
B
O
Null
End of any wrappers, at minimum including Request Message
Table SFDS-2 - Response Data for Command 0xD811 - Start Send File to Device (Secured)
Beginning of any wrappers, at minimum including Response Message
D811 = Start Send File to Device (Secured) - Command 0xD811
No parameters.
End of any wrappers, at minimum including Response Message
If the request started successfully, the Request Status in the message wrapper is OK, Started / Running, All good / requested operation was successful.
For additional support, please contact MagTek Support.
Table SFDS - 3 - Request Example
AA 00 81 04 01 04 D8 11 84 81 8F EE EE A1 19 81 05 03 03 06 02 08 84 00 85 00 A8 0A 81 02 11 02 82 00 86 00 88 00 A9 00 82 04 FF FF FF F0 83 08 C9 65 45 F2 97 69 85 B1 84 4E D8 11 81 04 00 00 03 00 A2 2B 81 04 00 00 02 99 82 01 04 83 20 87 A4 B3 54 61 C5 CB D3 1D DC BA 9D 65 25 5A D4 6A 22 FA 51 5E FD 65 87 AF AC A8 8C 4F AF 80 9B A3 14 38 31 30 38 33 30 33 30 33 30 33 30 33 33 33 30 33 30 87 01 01 9E 10 7D E4 27 C8 A0 70 72 08 19 0A 1E 0A 3F 48 BB F1
Table SFDS-5 - Response Example
AA 00 81 04 82 0C D8 11 82 04 00 00 00 00
Last updated