From 3b2e7178fbae0aaea1823f5e3d3b3d8af39a862d Mon Sep 17 00:00:00 2001 From: kormax <3392860+kormax@users.noreply.github.com> Date: Mon, 31 Jul 2023 16:11:15 +0300 Subject: [PATCH] Fix minor mistake --- README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 4baf32e..c45d5ee 100644 --- a/README.md +++ b/README.md @@ -399,12 +399,12 @@ Following protocols are considered "enhanced" as they implement an explicit stat Following protocols have implicit transaction status detection: -| Protocol name | Success condition | Failure condition | Notes | -| ------------- | ------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| CATHAY | DESELECT/TRESET after AID selection | DESELECT/TRESET before AID selection | | -| Felica | 0.5 second delay after TRESET if REQUEST_SERVICE(`0x02`) has been used. 5 second delay after TRESET otherwise | READ/WRITE commands with invalid keys | Current success condition causes lots of confusion for users, as a top-up machine may do a TRESET and an additional POLLING for data verification, but it causes a checkmark to appear thus misleading users, making them think that they can take the device out prematurely. | -| EMV | Cryptogram generation (EMV mode) or magstripe data read (MAG compatability mode) | DSELECT/TRESET before success condition | | -| VAS | Successful VAS GET DATA followed with a DESELECT/TRESET | DSELECT/TRESET after failed DESELECT/TRESET condition | | +| Protocol name | Success condition | Failure condition | Notes | +| ------------- | ------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| CATHAY | DESELECT/TRESET after AID selection | DESELECT/TRESET before AID selection | | +| Felica | 0.5 second delay after TRESET if REQUEST_SERVICE(`0x02`) has been used. 5 second delay after TRESET otherwise | READ/WRITE commands with invalid keys | Current success condition causes lots of confusion for users, as a top-up machine may do a TRESET and an additional POLLING for data verification, but it causes a checkmark to appear thus misleading users, making them think that they can take the device out prematurely. | +| EMV | Cryptogram generation (EMV mode) or magstripe data read (MAG compatability mode) | DSELECT/TRESET before success condition | | +| VAS | Successful VAS GET DATA followed with a DESELECT/TRESET | DSELECT/TRESET after failed VAS GET DATA | | There are other protocols, but those were left untested as I have no access to them: - iCLASS SE;