PMA82TP-BB
45 / 50
PROXRUNNER BLUETOOTH RFID SCANNER - Reference manual
SPRINGCARD, the SPRINGCARD logo, PRO ACTIVE and the PRO ACTIVE logo are registered trademarks of PRO ACTIVE SAS.
All other brand names, product names, or trademarks belong to their respective holders.
Information in this document is subject to change without notice. Reproduction without written permission of PRO ACTIVE is forbidden.
Items found in T,L,V blocks will overwrite data with the same tag already present
in reader’s non-volatile memory.
Set Len = 0 to delete an existing tag from the non-volatile memory, without
replacing it.
Last T,L,V of the configuration data block must be the (valid) signature of the
whole block, according to the HMAC-MD5 digital signature algorithm specified in
next chapter.
6.3.3. Mifare keys to be loaded into RC’s secure EEPROM
Keys to be loaded into RC’s secure EEPROM use the T,L,V scheme, as follow :
Tag (1 byte) =
h
80 + key index (see chapter “Mifare Classic Card Acceptance
Template”),
Len (1 byte) =
h
06,
Value is the Mifare key (6 bytes exactly).
6.4. D
IGITAL SIGNATURE
6.4.1. Size of file
File holding the signature (offset 4 in LOC.MAS) must be exactly 16-byte long.
6.4.2. Algorithm
This is the signature algorithm when default parameters in SGN.KEY are used :
Let
Content
be the 512-byte configuration block as written in the card
24
,
Let
SignKey
be the 16-byte key,
Diversify
SignKey
from card’s UID, using HMAC-MD5 diversification
algorithm
25
to get
DivKey
,
Compute
Sign
= HMAC-MD5 (
Block
) using
DivKey
26
.
The value of
SignKey
is confidential. Customers shall not try to change the key,
nor the signature algorithm.
24
This is the configuration data plus the Mifare keys to be loaded into RC’s secure EEPROM. Total size
is up to 512 bytes. Note that signature is computed over the whole file, including its padding,
whatever the used length is.
25
See next chapter “Security algorithms”
26
See next chapter “Security algorithms”
