Forum › MIFARE SDK › Problem authenticating a MIFARE Ultralight EV1 tag › Reply To: Problem authenticating a MIFARE Ultralight EV1 tag
Hi,
sorry but your response does not solve my problem. I have tested with Taplinx 1.1 (and 1.0) and the behavior is the same.
In fact, in the code snippet you posted they documented exactly the behavior I’m describing:
//Authenticate failed with timeout as Tag Lost exception which is expected as per the datasheet
Can I please have a reference where to the datasheet where this is documented? My guess is they are talking about this document (http://www.nxp.com/documents/data_sheet/MF0ULX1.pdf), but I can’t find this behavior documented anywhere. Furthermore, if that is the expected behavior please update the documentation of the Taplinx Library. The relevant parts of the documentation (https://www.mifare.net/files/advanced_javadoc/com/nxp/nfclib/ultralight/IUltralightEV1.html#authenticatePwd-byte:A- and https://www.mifare.net/files/advanced_javadoc/com/nxp/nfclib/ultralight/UltralightEV1.html#authenticatePwd-byte:A- which I linked in my original post) both state that the method should return a wrong pack when provided with the wrong password which is clearly not what the method is doing.
Finally, since the timeout is the expected behavior, is there a way to tell apart a connection error (e.g. the user removes the tag before the IO is complete) and an authentication error? As of now both situations will cause an exception with “Tag Lost” as message so there is no way to tell them apart.
As a side note, I find this answer quite disrespectful. I don’t get how they “obviously know” which version of the library I’m using when the behavior is the same in both versions of Taplinx (and I tested in both versions before posting my question). Furthermore, you finish your post saying “With the current release (version 1.1) of TapLinx there is no issue regarding Ultralight authentication.” yet the code snippet you posted clearly shows that the library behaves exactly as I’m describing.
sorry but your response does not solve my problem. I have tested with Taplinx 1.1 (and 1.0) and the behavior is the same.
In fact, in the code snippet you posted they documented exactly the behavior I’m describing:
//Authenticate failed with timeout as Tag Lost exception which is expected as per the datasheet
Can I please have a reference where to the datasheet where this is documented? My guess is they are talking about this document (http://www.nxp.com/documents/data_sheet/MF0ULX1.pdf), but I can’t find this behavior documented anywhere. Furthermore, if that is the expected behavior please update the documentation of the Taplinx Library. The relevant parts of the documentation (https://www.mifare.net/files/advanced_javadoc/com/nxp/nfclib/ultralight/IUltralightEV1.html#authenticatePwd-byte:A- and https://www.mifare.net/files/advanced_javadoc/com/nxp/nfclib/ultralight/UltralightEV1.html#authenticatePwd-byte:A- which I linked in my original post) both state that the method should return a wrong pack when provided with the wrong password which is clearly not what the method is doing.
Finally, since the timeout is the expected behavior, is there a way to tell apart a connection error (e.g. the user removes the tag before the IO is complete) and an authentication error? As of now both situations will cause an exception with “Tag Lost” as message so there is no way to tell them apart.
As a side note, I find this answer quite disrespectful. I don’t get how they “obviously know” which version of the library I’m using when the behavior is the same in both versions of Taplinx (and I tested in both versions before posting my question). Furthermore, you finish your post saying “With the current release (version 1.1) of TapLinx there is no issue regarding Ultralight authentication.” yet the code snippet you posted clearly shows that the library behaves exactly as I’m describing.
+ 0
|
- 0