simtrace

simtrace@lists.osmocom.org

346 discussions

power consumption
by Suraev 07 Aug '15

07 Aug '15

Hi. I wonder if it's possible to measure how much power is consumed by the sim card using simtrace? After all it's the only source of power for the sim card anyway. cheers, Max.

3 2

simtrace splict ATR and APDU
by yue ma 30 Jun '15

30 Jun '15

Hi , I ordered a simtrace and found the problem written in know issue, the host can't split ATR and APDU but only report detect ATR. Could you please tell me where I can find the firmware and how to update it? Best Regards Ma Yue <para>For some cards the firmware does not send an USB message at57 <http://code.metager.de/source/xref/osmocom/simtrace/docs/chapters/using_sni…> the end of the ATR. The ATR and first APDU will be send in one message58 <http://code.metager.de/source/xref/osmocom/simtrace/docs/chapters/using_sni…> and the host utility fails to split APDUs and nothing will be traced.59 <http://code.metager.de/source/xref/osmocom/simtrace/docs/chapters/using_sni…> A band-aid for the firmware exists and can be found on the mailinglist.60 <http://code.metager.de/source/xref/osmocom/simtrace/docs/chapters/using_sni…> </para>

1 0

APDU traces
by Stephan Malric 27 May '15

27 May '15

Dear all, To anybody having some experience with SimTrace : which APDU are traced and displayable in WIreshark ? APDU from ME to SIM ? From SIM to ME ? or both ? Best regards Stephan

2 1

Contact-less tracer
by Jérome Dufour 02 May '15

02 May '15

Dear all, Would anyone know where to get a contact-less tracer? Regards,Jerome.

1 0

Issue building SIMtrace firmware from OpenPCD repository
by Nick Poczynek 29 Apr '15

29 Apr '15

Hello, I'm unable to build the SIMtrace firmware according to the instructions on the wiki at http://bb.osmocom.org/trac/wiki/SIMtrace/Firmware. The GCC 4.5.2 ARM cross compiler has been installed and added to my path. Here is the output when I run make: ~/repos/openpcd/firmware$ make -f Makefile.dfu BOARD=SIMTRACE -------- begin (mode: RUN_FROM_ROM) -------- arm-elf-gcc (GCC) 4.5.2 Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Assembling (ARM-only): src/start/Cstartup.S arm-elf-gcc -c -mcpu=arm7tdmi -I. -x assembler-with-cpp -DRUN_FROM_ROM -D__AT91SAM7S256__ -Wa,-adhlns=src/start/Cstartup.lst,--gdwarf-2 -Iinclude/ -D__ASSEMBLY__ src/start/Cstartup.S -o src/start/Cstartup.o src/start/Cstartup.S:102:2: error: #error please define PIO_BOOTLDR for your board make: *** [src/start/Cstartup.o] Error 1 Has the SIMtrace target been removed from this repo? Looking through Makefile and Makefile.dfu, I don't see any references to the project. None of the checks on the $BOARD variable include a SIMTRACE option. Similarly, Cstartup.S only defines PIO_BOOTLDR for PCD, PICC, and OLIMEX boards. I'm still browsing through some other source files to see if I'm missing something obvious, but I'd appreciate any advice. Thanks, -Nick P.

1 0

APDU log
by de Miguel, Gorka 21 Apr '15

21 Apr '15

Dear friends, First of all, let me introduce myself. My name is Gorka De Miguel and I am working in my master´s thesis right now. On it, I am trying to do a man in the middle attack to my own cellphone and trying to obtain the data that reaches the SIM card. For that I am using a simtrace board. I have followed the user manual and the advises given in the web, but I am not able to make it work properly. Once I have simtrace executable created with the libosmocom and the rest of libraries in my computer in the way it is said in the web, I can execute it and some APDUs appear in the screen, but they seem to be not useful. Then I wanted to log them by using HTerm, to parse it and try to obtain the meaning of the APDUs. But the device is not recognized by the linux machine. I mean , it does not appear in the /dev directory. So it is imposible to reach to it and log the APDUs using a different program. I also tried to recognize the device using a windows machine, but it does not recognize it as there is not a simtrace driver for windows. Reached this point, my questions are the following ones; is there any way of logging de APDUS from the simtrace program? Is there any simtrace driver for windows? Do you know about anyone that was able to parse the APDUs and understand them well? Have anybody used HTerm? Is anybody able to understand the APDUs obtained? If yes, would it be possible to obtain his/her contact? Thank you in advance for all, every little advice will be really helpful for me, Regards Gorka De Miguel

2 1

Announcing OsmoDevCon 2015
by Harald Welte 13 Feb '15

13 Feb '15

Dear Osmocom.org project members, I'm happy to be able to announce the annual incarnation of OsmoDevCon. The Date is set for March 27 through 30. Venue: As usual, IN-Berlin e.V. in Berlin, Germany. Further details can be obtained from http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2015 Attendance, as usual, is restricted to people with an active history in the Project by contributions in terms of code, patches, discussions, documentation or in other form. = Registration = If you have wiki access, please add yourself to the #Requested section. Alternatively, you can send me private e-mail about it. After review, your (nick)name will be listed in the #Confirmed section. Looking forward to meeting all of you again soon! -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Latest patches to build firmware 0.5.3-6ea9-dirty
by Petrus Du Toit 05 Dec '14

05 Dec '14

Hi, I have been trying to follow the steps in the post with subject "firmware 0.5.3-6ea9-dirty Ubuntu howto" on 2014-11-11 by pkix as I am having the same problem where simtrace just stops tracing some time after displaying garbage APDUs. None of attachement links in this post work (Error 404) so I cannot download the patches or the firmware. Please could someone tell me where to find the latest patches (unofficial, official) for the firmware and simtrace source. I have been trying to look on the mailing list but there are only archives for November 2014. Thank you in advance. Petrus Du Toit DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. SWIFTNET and any of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. Thank you.

1 0

Incomplete trace (due to high-speed SIM?)
by Min Xu 18 Nov '14

18 Nov '14

*Holger Hans Peter Freyther* holger at freyther.de <simtrace%40lists.osmocom.org?Subject=Re%3A%20Incomplete%20trace%20%28due%20to%20high-speed%20SIM%3F%29&In-Reply-To=%3C20130522102301.GP14728%40xiaoyu.lan%3E> *Wed May 22 12:23:01 CEST 2013* | On Tue, May 21, 2013 at 03:53:45PM +0200, Arthur Léna wrote: | >* I tried booting the iPhone using 2 different SIMs (this one from * | >* Free Mobile and another one) and the trace seems very short using | *>* the Free Mobile in comparison to the other one. By parsing the ATRs | *>* of both SIMs, I found out that the communication is done at 312500 | *>* bits/s with the Free Mobile SIM and only 78125 bits/s (for a clock | *>* running at 5MHz). Could this explain the loss of entire ADPUs by the * | >* tracer? If yes, is there a way to remedy to this problem (firmware * | >* update for example). *| Some people reported success by reducing the size of buffered bytes in the | firmware. | holger Holger There appears to be numerous references to "decrease the buffer in the firmware" to workaround the problem of losing bytes... but can you clarify which buffer to decrease, in which source file? I am guessing it's the req_ctx.c / req_ctx.h? Thanks

7 19

firmware 0.5.3-6ea9-dirty Ubuntu howto
by pkix 11 Nov '14

11 Nov '14

Problem: Latest official simtrace firmware v0.5 fails to trace some smart cards. The APDU output is meaningless and tracing stops after displaying few garbage APDUs. There is unofficial firmware "0.5.3-6ea9-dirty" which tries to fix the problem. Here are step-by-step instructions how to try out firmware "0.5.3-6ea9-dirty". Updating simtrace firmware: sudo apt-get install dfu-util wget http://lists.osmocom.org/pipermail/simtrace/attachments/20140624/a17d1070/a… sudo dfu-util -d 16c0:0762 -a0 -D ./attachment-0001.bin -R Now connect debug interface and press "reset" button on simtrace. You should see: sudo cu -l /dev/ttyUSB0 -s 115200 [000002] Version 0.5.3-6ea9-dirty compiled 20140624-112040 by min@Wolfgang Patching simtrace host software: sudo apt-get install libusb-1.0-0-dev wget https://launchpad.net/~osmobuntu/+archive/ubuntu/ppa/+files/libosmocore-dev… wget https://launchpad.net/~osmobuntu/+archive/ubuntu/ppa/+files/libosmocore_0.5… sudo dpkg -i libosmocore_0.5.3+git1-1_amd64.deb sudo dpkg -i libosmocore-dev_0.5.3+git1-1_amd64.deb git clone git://git.osmocom.org/simtrace cd simtrace git checkout e179a32048e cd host wget http://lists.osmocom.org/pipermail/simtrace/attachments/20141023/4e37cb7d/a… patch -p2 < attachment.bin make sudo ./simtrace Report success or failure to mxu(a)sanjole.com .

1 0

← Newer
1
...
17
18
19
20
21
22
23
...
35
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

simtrace