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/.
Harald Welte laforge at gnumonks.orgHi Lukas, On Fri, Dec 16, 2011 at 09:51:20AM +0100, Lukas Kuzmiak wrote: > I've generated some more data by putting in couple more osmo_hexdump()s. thanks. > But as I said yesterday, it seems some bytes from the actual data seems to > be marked with ATR flag in the firmware itself and since then the data come > somehow scrambled or shifted and parser can't put it together anymore. > Correct me if I'm mistaken but from what I've observed the first message > coming from USB always contains only ATR and has that ATR flag, I don't see > how simtrace sw could parse ATR from data bytes. yes, all the traffic is in your trace, it is simply a matter of not detecting properly where the ATR / APDU boundary is. > Let me know if this is sufficient somehow or you think the SIM will be > better, I can mail you the sim even today if you think it'll help more than > this trace. I think the trace is fine, I just need to find some time to actually look harder at the traces and the code. I'm not sure when that will be, things are quite crazy here right now :/ -- - Harald Welte <laforge at gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)