Forum › MIFARE SDK › Problem authenticating a MIFARE Ultralight EV1 tag › Reply To: Problem authenticating a MIFARE Ultralight EV1 tag
Hi Zhaoyu and Jorge,
I understand your point. From the view of a programmer it is annoying, to get time outs if something is going wrong. But here we must bear in mind that this behavior is defined in ISO/IEC 14443-3. This specification does not include a transport layer! It is intended for simple tags and the MIFARE Ultralight EV1 is at the end a “tag with features”.
If you look to page 8 of the Ultralight EV1 datasheet you will find the sate diagram. If an error, unexpected command or other failure occurs, the state machine goes into HALT or IDLE state. For an ISO/IEC 14443-3 compliant tag there is no other choice.
The password protection is one of the interesting features of the Ultralight EV1. But I must make this very clear: the password protection of the Ultralight EV1 is NOT a high security protection! If you need this, you should always prefer an ISO/IEC14444-4 product like MIFARE DESFire EV1/EV2 or MIFARE Plus in SL3 (a Plus in SL1 is MIFARE Classic compliant). The ISO/IEC 14444-4 specification defines a transport layer with an error detection and recovery (you will get always an error code if something went wrong). With this products you have a strong encrypted communication with AES128 cipher and a lot of other security features.
The result is: due to the definition of the ISO/IEC 14443-3 specification there is no solution what can be implemented in software to change this behavior.
Sorry,
The TapLinx team
I understand your point. From the view of a programmer it is annoying, to get time outs if something is going wrong. But here we must bear in mind that this behavior is defined in ISO/IEC 14443-3. This specification does not include a transport layer! It is intended for simple tags and the MIFARE Ultralight EV1 is at the end a “tag with features”.
If you look to page 8 of the Ultralight EV1 datasheet you will find the sate diagram. If an error, unexpected command or other failure occurs, the state machine goes into HALT or IDLE state. For an ISO/IEC 14443-3 compliant tag there is no other choice.
The password protection is one of the interesting features of the Ultralight EV1. But I must make this very clear: the password protection of the Ultralight EV1 is NOT a high security protection! If you need this, you should always prefer an ISO/IEC14444-4 product like MIFARE DESFire EV1/EV2 or MIFARE Plus in SL3 (a Plus in SL1 is MIFARE Classic compliant). The ISO/IEC 14444-4 specification defines a transport layer with an error detection and recovery (you will get always an error code if something went wrong). With this products you have a strong encrypted communication with AES128 cipher and a lot of other security features.
The result is: due to the definition of the ISO/IEC 14443-3 specification there is no solution what can be implemented in software to change this behavior.
Sorry,
The TapLinx team
+ 0
|
- 0