Forum › MIFARE SmartCard IC`s › MIFARE Classic and SAM AV2 Authentication › Reply To: MIFARE Classic and SAM AV2 Authentication
Hi Adnan,
How a MIFARE Classic is managed, is defined by reader manufacturer. You need definitely the user manual of the reader. For example, I have a HID Omnikey reader (contact and contactless). In the “Contactless Smart Card Readers - DEVELOPER GUIDE” from HID I found on page 17 a section about “MIFARE card”. The reader support the following commands: GetUID, Loadkey, Authenticate, Verify, Update Binary, Read Binary. This commands are implemented according PCSC 2.01. For the commands Increment and Decrement they have a proprietary extension of PCSC ADPU sequence, printed in the manual.
The document “Interoperability Specification for ICCs and Personal Computer Systems - Part 3. Requirements for PC-Connected Interface Devices” define the APDU sequences for the MIFARE Classic, tagged as “MIFARE Card”. Due the Classic architecture, you must first load a key (the APDU sequence is shown in the paper) and then make an authentication against the loaded key number.
Sorry, not straightforward, but with this information you should solve your problem.
The TapLinx team
How a MIFARE Classic is managed, is defined by reader manufacturer. You need definitely the user manual of the reader. For example, I have a HID Omnikey reader (contact and contactless). In the “Contactless Smart Card Readers - DEVELOPER GUIDE” from HID I found on page 17 a section about “MIFARE card”. The reader support the following commands: GetUID, Loadkey, Authenticate, Verify, Update Binary, Read Binary. This commands are implemented according PCSC 2.01. For the commands Increment and Decrement they have a proprietary extension of PCSC ADPU sequence, printed in the manual.
The document “Interoperability Specification for ICCs and Personal Computer Systems - Part 3. Requirements for PC-Connected Interface Devices” define the APDU sequences for the MIFARE Classic, tagged as “MIFARE Card”. Due the Classic architecture, you must first load a key (the APDU sequence is shown in the paper) and then make an authentication against the loaded key number.
Sorry, not straightforward, but with this information you should solve your problem.
The TapLinx team
+ 0
|
- 0