Seedkeeper cards have their own secure logging system stored in the chip card memory.
These logs can only be accessed in read mode, the chip is responsible for creation/erasure of logs in memeory.
These logs should be accessible for consultation by the user via the "Card Information" menu, using a new button "Card Logs". Tjis should open a new screens with the logs shown in an array.
Each log is 7 bytes long and contains the following info:
ins: the (byte) instructiion code of the operation logged
sw: the (short) result such as 0x9000 for operation successful
sid1: (short) optional sid parameter of the operation (the sid of the secret on which operation has been performed)
sid2: (short) optional sid parameter of the authentikey for operation when secret is encrypted
For the next release, it is sufficient to display a simple array of logs with instruction text (english only), core result in hex, and sid(s) in number.
Seedkeeper cards have their own secure logging system stored in the chip card memory. These logs can only be accessed in read mode, the chip is responsible for creation/erasure of logs in memeory.
These logs should be accessible for consultation by the user via the "Card Information" menu, using a new button "Card Logs". Tjis should open a new screens with the logs shown in an array.
The logs can be fetched from the cards using cmdSet.seedkeeperPrintLogs().
Each log is 7 bytes long and contains the following info:
For ins byte, a list of instruction is available here: https://github.com/Toporin/Satochip-Java/blob/6df0a246893f3d47b05945d1dde4ae2be4800ec5/satochip-lib/src/main/java/org/satochip/client/Constants.java#L18
For the next release, it is sufficient to display a simple array of logs with instruction text (english only), core result in hex, and sid(s) in number.