Tools

Kanest Log Extract

Drop a test log from KaNest-ICC (text or XML) and get every APDU exchange back in two formats: a readable trace with command names, timestamps and status words, and a raw list with one APDU per line, ready to paste into another tool.

Your log stays on your device. The file is read and processed in your browser; nothing is uploaded. This tool is independent and not affiliated with the maker of the test tool.

Drop a Kanest log here (.txt or .xml) or Choose a file No file loaded.

Or paste the content of the log

Readable trace

Command name, C-APDU and R-APDU with timestamps, status word and its meaning, grouped by transaction.

One APDU per line

Commands and responses alternate, in order. Each response ends with its status word. A <tap> line marks each SELECT PPSE (contactless), an <insert> line each SELECT PSE (contact), and a <mute> line replaces the response to a command the card never answered. The file starts with the terminal's dynamic data for each transaction (9A, 9F21, 9F37, 9F6A, DF8301), read from the commands along the card's DOLs; a tag is written alone when its value was not found.

How it works

What it reads

Text logs (.txt): each command is a line starting with <- and each response a line starting with ->, followed by the bytes in hex, with a timestamp. Each card power-on (Vcc On) that carries APDUs is treated as a transaction. The test case name, the tool version and the verdict (from the passed and failed counts) are read from the log. XML logs (.xml) are also accepted; they have no timestamps.

Commands that get no response

A Command with an empty or missing Response is written as a <mute> line in the one-per-line format. For the dynamic data, values the reader reports in its transaction details (for example DE_9A or DE_9F37) are used when they cannot be read from the commands.

What to do next

Paste any response into the TLV parser to decode it, or take a SELECT PPSE response and the reader configuration to the Entry Point simulator.