Problems

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/.

Martin Paljak martin at martinpaljak.net
Wed Jan 25 16:10:13 UTC 2012


Hello,



On Wed, Jan 25, 2012 at 17:57, jeremy brookfield
<jeremy.brookfield at percula.com> wrote:
> Hi 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.)

The problem and solution is actually pretty simple in my case.

A patch is attached.

Next task: fix some "malformed packets" in Wireshark, which seem to be
unhandled opcodes for sim toolkit (?).

Martin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-apdu_split-correctly-handle-Le-00-which-means-256.patch
Type: application/octet-stream
Size: 736 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/simtrace/attachments/20120125/9050e7fe/attachment.obj>


More information about the simtrace mailing list