Elatec GmbH
Page 28 of 65
7.4.1.3 Mifare®
PLUS Login ‘nl’
Mifare® PLUS offers various authentication features to the user. Depending on the desired transaction
or configured security level of the transponder, the appropriate authentication procedure must be
chosen by the user. The reader always demands an AES key for authentication; if the transponder is
configured to security level 2, optionally a Crypto1 key can be passed to the reader. This enables the
reader to compute the appropriate session key for further communication ciphered by the Mifare®
Crypto1 algorithm. The Crypto1 login is performed automatically after AES authentication.
The login procedure is also used to switch a transponder to a higher security level. Furthermore, an
optional AES-authentication can be done in SL1 using the SL1 card authentication key.
Command:
‘nl[Sector / KeyNumber][KeyType][KeyAES][KeyCrypto1]’
Parameters
Description
[Sector /
KeyNumber]
Sector- or Keynumber, valid range 00h
– 2Ch.
00h … 27h:
Parameter addresses a data sector
28h:
Card master key
29h:
Card configuration key
2Ah:
Level 2 switch key
2Bh:
Level 3 switch key
2Ch:
SL1 card authentication key
[KeyType]
AAh:
authenticate with key type A
BBh:
authenticate with key type B
[KeyAES]
Enter key manually (16 bytes) or tell the reader to login with a stored EEPROM key (1 byte). EEPROM
keys are range 50h … 5Fh
[KeyCrypto1]
Enter key manually (6 bytes), or tell the reader to generate the Crypto1 session key using either a stored
EEPROM key or a transport key (1 byte). EEPROM keys are range 10h … 2Fh, Transport keys are
indicated by AA/BB/FF
Answer
Answer
Description
‘L<CR><LF>’
Login / Authentication / Security level switch success
‘F<CR><LF>’
Error: general failure
‘N<CR><LF>’
Error: no tag in the field or the tag does not respond
