simtrace

simtrace@lists.osmocom.org

350 discussions

new APDU command - how?
by Ale Ch 31 Oct '17

31 Oct '17

Hi! Tell me please, how to add new APDU command discription to see it in Wireshak log? Where in source code lay this command description? regards Alex

2 1

can't open USB device
by Ale Ch 26 Oct '17

26 Oct '17

Dear collegues, could you help me to start using SIMtrace board? I have bought SIMtrace board v1.4 from symocom shop. I have got sources from github but cannot (it is strange) built user manual on my ubuntu computer. BUT I am successfully built simtrace application but it cannot recognize the board. >user@lnkd149:~/OSMOCOM/simtrace/host$ ./simtrace >simtrace - GSM SIM and smartcard tracing >(C) 2010 by Harald Welte <laforge(a)gnumonks.org> > >can't open USB device that message I have received on my screen... Could you advise something? regards Alex

2 2

Planning for OsmoCon + OsmoDevCon
by Harald Welte 14 Oct '17

14 Oct '17

[cross-post to many lists, please follow-up-to openbsc(a)lists.osmocom.org] Dear all, time is flying, and I would like to start early with discussions and planning about OsmoCon and OsmoDevCon in 2018. It helps to start early. Side note: We have some pending issues about the events from last year at http://osmocom.org/projects/osmo-dev-con/issues - I've incorporated them in the text below. == OsmoDevCon == For OsmoDevCon, I think it's easy: We keep it as-is. Same procedure as every year, which means: * same venue, same catering options * same concept of 'anyone contributing to Osmocom can apply for registration until all seats are taken' * same idea of inviting some few speaker[s] doing other FOSS mobile communications work to join us The parts that we need to change, IMHO: * don't reduce from 4 to 3 days like last year. Have full 4 days again * sort topics per day / half-day, i.e. have "GSM/UMTS Cellular Infrastructure" days for BTS/BSC/NITB/MSC/HLR/SGSN/GGSN & Co, but then have other days for other projects. This would enable people not interested in the [continued evolvement] of the cellular projects be able to skip those days, or to simply meet in an adjacent room for parallel hacking sessions/discussions * try to be a bit more structured with the schedule in general. The existing approach works for people who attend all the event all day long, but not so well for people with other plans / limited time Any further change requests or topics to discuss? Please note that Pablo Neira has offered to kindly host an OsmoDevCon in Seville (Spain). I've attended a number of netfilter workshops he organized there, and he's doing a great job! However, given the large number of attendees from Berlin (and Germany in general), I think this would make things more complicated, and more expensive for most attendees. If you disagree with that assessment: I'm open for having the discussion, I just thought it's more practical/economic to do it in Berlin. === 10 year Anniversary Party === Given that 2018 marks the 10 year anniversary of Dieter and me hacking with the Siemens BS-11 in 2008, I think the 2018 incarnation deserves some special celebration of some form. I have no concrete idea yet, but for sure we should so something, and it should be at/around OsmoDevCon. And for sure we should have a BS-11 around :) == OsmoCon == The public OsmoCon was welcomed and was a success. However, let's start this discussion with a review of last years event. === Registration === * Registrations came in way too late. Two weeks ahead of the event, we were considering to cancel it. And then within the last few days, we had to turn people down due to limited seating capacity * To make planning more reliable, we see on other option but to significantly raise the registration fee combined with an equally significant discount for early booking === Duration === * Many people requested multiple days rather than just one, in order to make more out of (long distance) travels. This is obvious, but as we had no idea how many people would attend at all (or if we have to cancel due to lack of attendance), planning multiple days in the first incarnation would have been high risk and a multitude of work * I would suggest to expand to two or even three days this week, possibly one days with tutorials and the other day with tech talks * Slightly less crammed schedule due to multiple days === Venue === We recognize this yearso venue was not the best option, due to * Bad ventilation in the basemenet * Difficult to find * No space next to the conference room where people can meet / hang out in parallel to talks (not everyone attends every talk) I still like the "understatement" of the venue. I'd prefer any hostel / non-profit / hackerspace / university over luxurious hotels any time. Going to an expensive venue means more or less automatically more expensive ticket fees, which again is more likely to exclude pure community members without a commercial activity related to Osmocom. So any future venue would ideally: * be able to hold slightly more people than this year * have a second room or large lobby in which people can meet for extended coffee breaks in parallel to some talks, as needed * be slightly easier to find (and we have to put up some signs outside and in the lobby) * have better WiFi and/or wired connectivity === Programme / Format === * less crammed over multiple days * some more "interactive" formats were requested, for users to provide feedback to developers * there was some discussion about topics / speakers in redmine last year, but not too much participation [until it was too late]. * I'd suggest a more formal CfP process with a submission deadline that allows us to publish a preliminary schedule long ahead of the event === Video Recordings === I think they were a big success, and it was a very big surprise that the CCC Video Operations Center was volunteering to help such a small and niche-interest event like OsmoCon. We should make sure that we can repeat this for 2018. == Dates / Frequency == Having OsmoCon and OsmoDevCon back to back becomes somewhat long, if OsmoCon is 2-3 days and OsmoDevCon is 4 days. Basically we're looking at a full week for those of you who would like to attend both events. But then, I think the number of people attending both events is actually not all that big. Without checking the details, I think not more than half of the OsmoDevCon attendees were attending OsmoCon. I would expect that tendency to remain or even increase. I still think it's good to keep them back-to-back. In terms of frequency, I would actually suggest we move to a 6-month cycle rather than a 12-month cycle. There's a lot of development going on at all time. I understand that not everyone is able to attend two events just on Osmocom, especially if it's a spare time / hobby type activity. That's ok, I think there's no problem with attending either of the two only, and catching up by video recordings and/or mail on the other. The qeustion is: Should that second event be developer-oriented or user-oriented? Or again both? Any comments here? Ok, that was a somewhat lengthy e-mail. Please make sure to provide any feedback you may have as early as possible, to increase the chances of your feedback being reflected in the planning. Happy hacking, Harald -- - 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

[PATCH] firmware: Makefiles: enable changing toolchain
by Denis 'GNUtoo' Carikli 05 Oct '17

05 Oct '17

Without that the user was expected to either patch the Makefiles or to get a toolchain with the arm-elf- prefix. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo(a)no-log.org> --- firmware/Makefile | 13 +++++++------ firmware/Makefile.dfu | 13 +++++++------ 2 files changed, 14 insertions(+), 12 deletions(-) diff --git a/firmware/Makefile b/firmware/Makefile index 350b0dc..1581a1f 100644 --- a/firmware/Makefile +++ b/firmware/Makefile @@ -352,12 +352,13 @@ LPC21ISP_CONTROL = -control # Define programs and commands. SHELL = sh -CC = arm-elf-gcc -CPP = arm-elf-g++ -OBJCOPY = arm-elf-objcopy -OBJDUMP = arm-elf-objdump -SIZE = arm-elf-size -NM = arm-elf-nm +CROSS_COMPILE ?= arm-elf- +CC = $(CROSS_COMPILE)gcc +CPP = $(CROSS_COMPILE)g++ +OBJCOPY = $(CROSS_COMPILE)objcopy +OBJDUMP = $(CROSS_COMPILE)objdump +SIZE = $(CROSS_COMPILE)size +NM = $(CROSS_COMPILE)nm REMOVE = rm -f COPY = cp diff --git a/firmware/Makefile.dfu b/firmware/Makefile.dfu index 3c797ef..1e9e71c 100644 --- a/firmware/Makefile.dfu +++ b/firmware/Makefile.dfu @@ -303,12 +303,13 @@ LPC21ISP_CONTROL = -control # Define programs and commands. SHELL = sh -CC = arm-elf-gcc -CPP = arm-elf-g++ -OBJCOPY = arm-elf-objcopy -OBJDUMP = arm-elf-objdump -SIZE = arm-elf-size -NM = arm-elf-nm +CROSS_COMPILE ?= arm-elf- +CC = $(CROSS_COMPILE)gcc +CPP = $(CROSS_COMPILE)g++ +OBJCOPY = $(CROSS_COMPILE)objcopy +OBJDUMP = $(CROSS_COMPILE)objdump +SIZE = $(CROSS_COMPILE)size +NM = $(CROSS_COMPILE)nm REMOVE = rm -f COPY = cp -- 2.14.1

2 1

simtrace as a remote sim solution
by pozsy＠uhulinux.hu 01 Oct '17

01 Oct '17

Hi All, Just found this project which seems to be quite interesting to me. Tried to read through all the information on the project page before asking, but not everything is clear yet :) So what I would like to achieve is basically the man-in-the-middle (mitm) mode. I do not actually need to modify any communication on its way, all I would like to do is to have: a) the sim card in a reader connected to host (A), while b) the gsm module is connected to an other host (B) and relaying their communication back and forth through some IP network. I guess I would need two pieces of simtrace hardware for that, as well as firmware and software modifications. Now the questions :) - Do you think this could work with the current hw/fw design? - Has anyone done something similar in the past? - What would be the maximum network delay allowed? - Do you know of any alternative solutions for my needs? Would be great to hear from you. Thanks, Balazs ps: I would also be willing to pay for professional consultancy services on this topic.

2 1

Baud rate
by Vishal Vaidhyanathan 17 Jul '17

17 Jul '17

Hi, What is the BAUD rate of the phone clock? You must know it for sniffing the communication between the phone and SIM card. And does Wireshark output all the communication between the phone and the SIM card? Please let me know. Thanks, Vishal

3 7

Simtrace
by Vishal Vaidhyanathan 13 Jul '17

13 Jul '17

Hi, We purchased the Simtrace HW kit from you guys and I tried to sniff the communication between the sim and an iPhone 6. After installing the firmware and running simtrace, I was able to view the results on Wireshark. Looking into the results, all the field’s like EF.ICCID, EF.IMSI and EF.Keys had the same number (APDU Payload). I got the numbers like ICCID and IMSI and it didn’t match them. Do you have any idea where the issue might be? Please let me know Regards, Vishal

2 1

simtrace/openpcd build problem
by Piotr Chytla 26 Jun '17

26 Jun '17

Hi, I've tried to build lastest HEAD of openpcd and building are failing on unkown uint8_t/16_t/32_t types ( on GCC 4.8.4) . Makefile/Makefile.dfu ggives the same errors. I've already tried to build this on debian 7.11 - gcc 4.5.2, and debian jessie 8.7 / gcc 4.8.4 ( arm-none-eabi) and it seems same . Reverting commit 373c172ab858102e1818c8476ab1a2b290685cda fixes problem . [..] GCC 4.5.2 -------- 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. scripts/mkcompile_h > include/compile.h Compiling C (ARM-only): src/start/Cstartup_SAM7.c arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DBOARD=SIMTRACE -DRUN_FROM_ROM -D__MS_types__ -D__LIBRFID__ -DSIMTRACE -D__AT91SAM7S128__ -Isrc/simtrace -Iinclude -Isrc -Os -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wbad-function-cast -Wsign-compare -Waggregate-return -Wa,-adhlns=src/start/Cstartup_SAM7.lst -MD -MP -MF .dep/Cstartup_SAM7.o.d -Wnested-externs -std=gnu99 src/start/Cstartup_SAM7.c -o src/start/Cstartup_SAM7.o Compiling C (ARM-only): lib/lib_AT91SAM7.c arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DBOARD=SIMTRACE -DRUN_FROM_ROM -D__MS_types__ -D__LIBRFID__ -DSIMTRACE -D__AT91SAM7S128__ -Isrc/simtrace -Iinclude -Isrc -Os -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wbad-function-cast -Wsign-compare -Waggregate-return -Wa,-adhlns=lib/lib_AT91SAM7.lst -MD -MP -MF .dep/lib_AT91SAM7.o.d -Wnested-externs -std=gnu99 lib/lib_AT91SAM7.c -o lib/lib_AT91SAM7.o Compiling C (ARM-only): src/dfu/dfu.c arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DBOARD=SIMTRACE -DRUN_FROM_ROM -D__MS_types__ -D__LIBRFID__ -DSIMTRACE -D__AT91SAM7S128__ -Isrc/simtrace -Iinclude -Isrc -Os -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wbad-function-cast -Wsign-compare -Waggregate-return -Wa,-adhlns=src/dfu/dfu.lst -MD -MP -MF .dep/dfu.o.d -Wnested-externs -std=gnu99 src/dfu/dfu.c -o src/dfu/dfu.o In file included from src/dfu/dfu.c:24:0: include/usb_ch9.h:122:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:172:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:181:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:234:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:257:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:271:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:289:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:320:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:337:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:351:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:363:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:381:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:394:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:406:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:423:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:434:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:442:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:473:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:495:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_ch9.h:511:2: error: expected specifier-qualifier-list before ‘uint8_t’ In file included from src/dfu/dfu.c:25:0: include/usb_dfu.h:18:2: error: expected specifier-qualifier-list before ‘uint8_t’ include/usb_dfu.h:44:2: error: expected specifier-qualifier-list before ‘uint8_t’ In file included from src/dfu/dfu.c:29:0: src/simtrace/usb_strings_dfu.h:11:2: error: expected specifier-qualifier-list before ‘uint16_t’ src/simtrace/usb_strings_dfu.h:14:3: error: unknown field ‘bLength’ specified in initializer src/simtrace/usb_strings_dfu.h:14:64: error: ‘uint16_t’ undeclared here (not in a function) [..] [..] GCC 4.8.4 -------- begin (mode: RUN_FROM_ROM) -------- arm-elf-gcc (4.8.4-1+11-1) 4.8.4 20141219 (release) Copyright (C) 2013 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. scripts/mkcompile_h > include/compile.h gcc scripts/usbstring.c -o scripts/usbstring cat src/picc/usb_strings_dfu.txt | ./scripts/usbstring > src/picc/usb_strings_dfu.h cat src/pcd/usb_strings_dfu.txt | ./scripts/usbstring > src/pcd/usb_strings_dfu.h cat src/simtrace/usb_strings_dfu.txt | ./scripts/usbstring > src/simtrace/usb_strings_dfu.h Compiling C (ARM-only): src/start/Cstartup_SAM7.c arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DBOARD=SIMTRACE -DRUN_FROM_ROM -D__MS_types__ -D__LIBRFID__ -DSIMTRACE -D__AT91SAM7S128__ -Isrc/simtrace -Iinclude -Isrc -Os -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wbad-function-cast -Wsign-compare -Waggregate-return -Wa,-adhlns=src/start/Cstartup_SAM7.lst -MD -MP -MF .dep/Cstartup_SAM7.o.d -Wnested-externs -std=gnu99 src/start/Cstartup_SAM7.c -o src/start/Cstartup_SAM7.o Compiling C (ARM-only): lib/lib_AT91SAM7.c arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DBOARD=SIMTRACE -DRUN_FROM_ROM -D__MS_types__ -D__LIBRFID__ -DSIMTRACE -D__AT91SAM7S128__ -Isrc/simtrace -Iinclude -Isrc -Os -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wbad-function-cast -Wsign-compare -Waggregate-return -Wa,-adhlns=lib/lib_AT91SAM7.lst -MD -MP -MF .dep/lib_AT91SAM7.o.d -Wnested-externs -std=gnu99 lib/lib_AT91SAM7.c -o lib/lib_AT91SAM7.o Compiling C (ARM-only): src/dfu/dfu.c arm-elf-gcc -c -mcpu=arm7tdmi -I. -gdwarf-2 -DBOARD=SIMTRACE -DRUN_FROM_ROM -D__MS_types__ -D__LIBRFID__ -DSIMTRACE -D__AT91SAM7S128__ -Isrc/simtrace -Iinclude -Isrc -Os -Wall -Wextra -Wcast-align -Wimplicit -Wunused -Wpointer-arith -Wswitch -Wredundant-decls -Wreturn-type -Wshadow -Wbad-function-cast -Wsign-compare -Waggregate-return -Wa,-adhlns=src/dfu/dfu.lst -MD -MP -MF .dep/dfu.o.d -Wnested-externs -std=gnu99 src/dfu/dfu.c -o src/dfu/dfu.o In file included from src/dfu/dfu.c:24:0: include/usb_ch9.h:122:2: error: unknown type name 'uint8_t' uint8_t bRequestType; ^ include/usb_ch9.h:123:2: error: unknown type name 'uint8_t' uint8_t bRequest; ^ include/usb_ch9.h:124:2: error: unknown type name 'uint16_t' uint16_t wValue; ^ include/usb_ch9.h:125:2: error: unknown type name 'uint16_t' uint16_t wIndex; ^ include/usb_ch9.h:126:2: error: unknown type name 'uint16_t' uint16_t wLength; ^ include/usb_ch9.h:172:2: error: unknown type name 'uint8_t' uint8_t bLength; ^ include/usb_ch9.h:173:2: error: unknown type name 'uint8_t' uint8_t bDescriptorType; ^ include/usb_ch9.h:181:2: error: unknown type name 'uint8_t' uint8_t bLength; ^ include/usb_ch9.h:182:2: error: unknown type name 'uint8_t' uint8_t bDescriptorType; ^ include/usb_ch9.h:184:2: error: unknown type name 'uint16_t' uint16_t bcdUSB; ^ include/usb_ch9.h:185:2: error: unknown type name 'uint8_t' uint8_t bDeviceClass; ^ include/usb_ch9.h:186:2: error: unknown type name 'uint8_t' uint8_t bDeviceSubClass; ^ include/usb_ch9.h:187:2: error: unknown type name 'uint8_t' uint8_t bDeviceProtocol; ^ include/usb_ch9.h:188:2: error: unknown type name 'uint8_t' uint8_t bMaxPacketSize0; ^ include/usb_ch9.h:189:2: error: unknown type name 'uint16_t' uint16_t idVendor; ^ include/usb_ch9.h:190:2: error: unknown type name 'uint16_t' uint16_t idProduct; ^ include/usb_ch9.h:191:2: error: unknown type name 'uint16_t' uint16_t bcdDevice; ^ include/usb_ch9.h:192:2: error: unknown type name 'uint8_t' uint8_t iManufacturer; ^ include/usb_ch9.h:193:2: error: unknown type name 'uint8_t' uint8_t iProduct; ^ include/usb_ch9.h:194:2: error: unknown type name 'uint8_t' uint8_t iSerialNumber; ^ include/usb_ch9.h:195:2: error: unknown type name 'uint8_t' uint8_t bNumConfigurations; ^ include/usb_ch9.h:234:2: error: unknown type name 'uint8_t' uint8_t bLength; ^ include/usb_ch9.h:235:2: error: unknown type name 'uint8_t' uint8_t bDescriptorType; ^ include/usb_ch9.h:237:2: error: unknown type name 'uint16_t' uint16_t wTotalLength; ^ include/usb_ch9.h:238:2: error: unknown type name 'uint8_t' uint8_t bNumInterfaces; ^ include/usb_ch9.h:239:2: error: unknown type name 'uint8_t' uint8_t bConfigurationValue; ^ include/usb_ch9.h:240:2: error: unknown type name 'uint8_t' uint8_t iConfiguration; ^ include/usb_ch9.h:241:2: error: unknown type name 'uint8_t' uint8_t bmAttributes; ^ include/usb_ch9.h:242:2: error: unknown type name 'uint8_t' uint8_t bMaxPower; ^ include/usb_ch9.h:257:2: error: unknown type name 'uint8_t' uint8_t bLength; ^ include/usb_ch9.h:258:2: error: unknown type name 'uint8_t' uint8_t bDescriptorType; ^ include/usb_ch9.h:260:2: error: unknown type name 'uint16_t' uint16_t wData[0]; /* UTF-16LE encoded */ ^ include/usb_ch9.h:271:2: error: unknown type name 'uint8_t' uint8_t bLength; ^ include/usb_ch9.h:272:2: error: unknown type name 'uint8_t' uint8_t bDescriptorType; ^ include/usb_ch9.h:274:2: error: unknown type name 'uint8_t' uint8_t bInterfaceNumber; ^ include/usb_ch9.h:275:2: error: unknown type name 'uint8_t' uint8_t bAlternateSetting; ^ include/usb_ch9.h:276:2: error: unknown type name 'uint8_t' uint8_t bNumEndpoints; ^ include/usb_ch9.h:277:2: error: unknown type name 'uint8_t' uint8_t bInterfaceClass; ^ include/usb_ch9.h:278:2: error: unknown type name 'uint8_t' uint8_t bInterfaceSubClass; ^ include/usb_ch9.h:279:2: error: unknown type name 'uint8_t' uint8_t bInterfaceProtocol; ^ include/usb_ch9.h:280:2: error: unknown type name 'uint8_t' uint8_t iInterface; ^ include/usb_ch9.h:289:2: error: unknown type name 'uint8_t' uint8_t bLength; ^ include/usb_ch9.h:290:2: error: unknown type name 'uint8_t' uint8_t bDescriptorType; ^ include/usb_ch9.h:292:2: error: unknown type name 'uint8_t' uint8_t bEndpointAddress; ^ include/usb_ch9.h:293:2: error: unknown type name 'uint8_t' uint8_t bmAttributes; ^ include/usb_ch9.h:294:2: error: unknown type name 'uint16_t' uint16_t wMaxPacketSize; ^ include/usb_ch9.h:295:2: error: unknown type name 'uint8_t' uint8_t bInterval; ^ include/usb_ch9.h:320:2: error: unknown type name 'uint8_t' uint8_t bLength; ^ include/usb_ch9.h:321:2: error: unknown type name 'uint8_t' uint8_t bDescriptorType; ^ include/usb_ch9.h:323:2: error: unknown type name 'uint16_t' uint16_t bcdUSB; ^ include/usb_ch9.h:324:2: error: unknown type name 'uint8_t' uint8_t bDeviceClass; ^ include/usb_ch9.h:325:2: error: unknown type name 'uint8_t' uint8_t bDeviceSubClass; ^ include/usb_ch9.h:326:2: error: unknown type name 'uint8_t' uint8_t bDeviceProtocol; ^ include/usb_ch9.h:327:2: error: unknown type name 'uint8_t' uint8_t bMaxPacketSize0; ^ include/usb_ch9.h:328:2: error: unknown type name 'uint8_t' uint8_t bNumConfigurations; ^ include/usb_ch9.h:329:2: error: unknown type name 'uint8_t' uint8_t bRESERVED; ^ include/usb_ch9.h:337:2: error: unknown type name 'uint8_t' /pch -- Piotr Chytla <pch(a)packetconsulting.pl>

1 0

Feature #1724: Extend wireshark dissector for SIM/USIM traces
by Gerard Lawrence Pinto 18 Jun '17

18 Jun '17

Greetings, I have been working with wireshark and SIMtrace. And decided to extended the dissector for 'GET RESPONSE' (mf/df/ef) and 'STATUS' - according to the ETSI 11.11 Section 9.2.1 Page 39 - 41 and Page 46 (Definitions and Codings for response params) Keeping update with latest wireshark commits. I would like to commit to their gerrit. Please could you let me know here - if the output is as expected. Let me know your views/comments on the output so I can change it before commit. Also code can be viewed here 'https://github.com/GerardPinto/wireshark' (properly forked and synced with upstream) or reviewed by wireshark gerrit (Once I get your views on the output). (1) Get Response MF/DF: GSM SIM 11.11 1010 .... = Class Coding: ISO/IEC 7816-4 unless stated otherwise (0xa) .... 00.. = Secure Messaging Indication: No SM used between terminal and card (0x0) .... ..00 = Logical Channel number: 0 Instruction: GET RESPONSE (0xc0) Length of Expected Response Data: 32 RFU: 0x00 Total amt of memory not allocated to any of the DFs or EFs under the selected dir: 0x00 File ID: DF.GSM (0x7f20) Type of File: DF (0x02) RFU: 0000000000 Length of following data: 19 GSM Specific Data File Characteristics: 0xb3, Clock Stopping Indication: Not Allowed - unless at low level, Frequency Required for ENVELOPE cmd /AUTH algo, CHV1 Status .... 00.1 = Clock Stopping Indication: Not Allowed - unless at low level (0x1) .... ..1. = Frequency Required for ENVELOPE cmd /AUTH algo: 13/4 Mhz .011 .... = RFU: 0x3 1... .... = CHV1 Status: Enabled DFs in Current Directory: 0 EFs in Current Directory: 41 Number of CHVs, UNBLOCK CHVs and administrative codes: 4 RFU: 0x00 CHV1 status: 0x83, Secret Code initialized .... 0011 = False presentations remaining ('0' means blocked): 3 .000 .... = RFU: 0x0 1... .... = Secret Code initialized: Yes UNBLOCK CHV1 Status: 0x8a, Secret Code initialized .... 1010 = False presentations remaining ('0' means blocked): 10 .000 .... = RFU: 0x0 1... .... = Secret Code initialized: Yes CHV2 Status: 0x8a, Secret Code initialized .... 1010 = False presentations remaining ('0' means blocked): 10 .000 .... = RFU: 0x0 1... .... = Secret Code initialized: Yes UNBLOCK CHV2 Status: 0x8a, Secret Code initialized .... 1010 = False presentations remaining ('0' means blocked): 10 .000 .... = RFU: 0x0 1... .... = Secret Code initialized: Yes RFU: 0x00 Reserved for the Administrative Management: 030000bbda00000000 Status Word: 9000 Normal ending of the command (2) Get Response EF: GSM SIM 11.11 1010 .... = Class Coding: ISO/IEC 7816-4 unless stated otherwise (0xa) .... 00.. = Secure Messaging Indication: No SM used between terminal and card (0x0) .... ..00 = Logical Channel number: 0 Instruction: GET RESPONSE (0xc0) Length of Expected Response Data: 15 RFU: 0x00 File Size: 11 File ID: EF.LOCI (0x6f7e) Type of File: EF (0x04) EF response Byte 8: RFU: 00 Access Condition Byte 9: 0x00, UPDATE: Always (ALW), READ/SEEK: Always (ALW) .... 0000 = UPDATE: Always (ALW) (0x0) 0000 .... = READ/SEEK: Always (ALW) (0x0) Access Condition Byte 10: 0x14, INCREASE: Administrative Authority (ADM), RFU: Card Holder Verification1 (CHV1) .... 0100 = INCREASE: Administrative Authority (ADM) (0x4) 0001 .... = RFU: Card Holder Verification1 (CHV1) (0x1) Access Condition Byte 11: 0x01, INVALIDATE: Card Holder Verification1 (CHV1), REHABILITATE: Always (ALW) .... 0001 = INVALIDATE: Card Holder Verification1 (CHV1) (0x1) 0000 .... = REHABILITATE: Always (ALW) (0x0) File Status: 0x01, Validation Status .... ...1 = Validation Status: Not invalidated .... ..0. = RFU: 0x0 .... .0.. = Read Update Status: Not readable or updatable when invalidated 0000 0... = RFU: 0x00 Length of following data: 2 File Structure: Transparent (0x00) Length of a record: 0 Status Word: 9000 Normal ending of the command (3) STATUS ( ETSI 11.11 Section 9.2.2) says - The response parameters/data are identical to the response parameters/data of the SELECT command in case of an MF or DF. Thanks, Gerard

1 0

Current status of the SIMtrace project
by E:V:A 21 Mar '17

21 Mar '17

Dear Osmocom, I have been following your SIMtrace project for some time and wanted to build and try a few things. However, it seem that the project is abandoned since it has not been updated on your Wiki for ages. I know you guys are very busy with your many other and more interesting projects and that this project is very old, but we would still appreciate if you could at least try to keep your own GIT repo updated with the stuff you are showing on the wiki. For example, I cloned the SIMtrace and opened the schematics in KiCad only to find that the schematic is several HW versions behind the currently shown one. So my questions are: 1. Have you abandoned the project? 2. Where can I find/download the latest Firmware, KiCad (Schematics and PCB) design files? 3. There is a related project on GitHub that are using SIMtrace. However, the firmware there seem different. What is the current status of the firmware? Are you involved in that development? https://github.com/kamwar/simlabTrace If your answer to (1) is a Yes, then perhaps it would be better to publish your project to GitHub instead, so that other people can help and take over the maintenance? This is actually a great idea, reagrdless as your Redmine/cgit based git repo is very slow and hard to navigate and the bug tracking of GH is superior in simplicity to anything else freely available. Kind Regards, E:V:A

3 6

← Newer
1
...
13
14
15
16
17
18
19
...
35
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

simtrace