This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/simtrace@lists.osmocom.org/.
jeremy brookfield jeremy.brookfield at percula.comHi Martin, I'm seeing a similar issue when running with certain card types. After a few,correctly parsed APDUs, Simtrace is reporting the APDU as 2 bytes more than it actually is. In your trace 90 00 00 0a is reported at the end of a payload 90 00 is often the last two bytes of a response and 00 0a is a common begin to a new APDU (00 0a often indicates a "select" instruction.) Jeremy On Jan 25, 2012, at 2:55 PM, Martin Paljak wrote: > > > How exactly is the stream from the device supposed to be split into > APDU-s, a la PC/SC, with a request and a response? The current format > confuses me a bit. I understand that this is right now totally the > reponsibility of the parser. > > >