Copyright © 2010-2014, International Technologies & Systems Corp. All rights reserved.
Page 47 of 74
SecureMag User Manual
Track 1, 2 and 3 hashed
SecureMag reader uses SHA-1 to generate hashed data for both track 1, track 2
and track 3 unencrypted data. It is 20 bytes long for each track. This is provided
with two purposes in mind: One is for the host to ensure data integrity by
comparing this field with a SHA-1 hash of the decrypted Track data, prevent
unexpected noise in data transmission. The other purpose is to enable the host to
store a token of card data for future use without keeping the sensitive card holder
data. This token may be used for comparison with the stored hash data to
determine if they are from the same card.
Some Additional notes:
1.
Track status byte is defined as the following
Track Status (bit0, 1,2: T1,2,3 decode; bit 3,4,5: T1,2,3 sampling)
Sampling
Decoding
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Track 1 Empty
0
1
Track 2 Empty
0
1
Track 3 Empty
0
1
Track 1 Decoded
1
1
Track 2 Decoded
1
1
Track 3 Decoded
1
1
Track 1 Fail To
Decode
1
0
Track 2 Fail To
Decode
1
0
Track 3 Fail To
Decode
1
0
2.
Please be aware that track status byte in secured output is different from
track status bytes in OPOS head (called read error1 and read error2).
OPOS header will only be used in OPOS mode security level 1 and
level 2 and secure output only used in level 3 or level 4.
3.
For USB HID Secure Output, the output format is same as Secure
Output structure. No HID header is added. But the total length is the
HIDSIZE (560 bytes as described in USB enumeration. HIDSIZE is
subject to change. Software should auto adjust in case enumeration
changes). Unused bytes will be filled with 0x00. This applied to secure
Level 3 and Level 4 output, whether or not the data is encrypted.