From shafiulalam at gmail.com Wed Nov 5 16:10:42 2014 From: shafiulalam at gmail.com (Shafiul Alam) Date: Wed, 5 Nov 2014 16:10:42 +0000 Subject: Does SIMtrace work with 3G/4G USIM? Message-ID: Dear Correspondence, For my academic research, I am interested on the SIMTrace product. I need to know about the transmitted data between 3G/4G USIM and the ME. Does SIMtrace help me to know that? Kind regards, Shafi ________________________________ *(Mohammed Shafiul Alam Khan)* PhD Student, Information Security Group (ISG), Royal Holloway, University of London (RHUL), Egham, Surrey TW20 0EX, UK. Mobile # *074 5920 8017* Official E-mail # Mohammed.Khan.2013 at live.rhul.ac.uk AND Faculty (On Leave), Institute of Information Technology, University of Dhaka, Dhaka, BANGLADESH -------------- next part -------------- An HTML attachment was scrubbed... URL: From kevredon at mail.tsaitgaist.info Mon Nov 10 09:43:35 2014 From: kevredon at mail.tsaitgaist.info (=?iso-8859-1?Q?K=E9vin?= Redon) Date: Mon, 10 Nov 2014 10:43:35 +0100 Subject: Does SIMtrace work with 3G/4G USIM? In-Reply-To: References: Message-ID: <20141110094335.GF568@coil> On Wed, Nov 05, 2014 at 04:10:42PM +0000, Shafiul Alam wrote: > Dear Correspondence, > > For my academic research, I am interested on the SIMTrace product. I need > to know about the transmitted data between 3G/4G USIM and the ME. Does > SIMtrace help me to know that? If the card and the phone use the T=0 transmission protocol, then it works. Some phone may use the T=1 protocol, but this is not the general rule. The hardware also supports the T=1 protocol, but it has not been implemented in the software yet. Last detail: some phones use a high baudrate. if you see some data loss, try the alternative firmware described in the mailing list. From pkix at inbox.lv Tue Nov 11 09:01:05 2014 From: pkix at inbox.lv (pkix) Date: Tue, 11 Nov 2014 11:01:05 +0200 Subject: firmware 0.5.3-6ea9-dirty Ubuntu howto Message-ID: <5461D051.3070200@inbox.lv> 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/attachment-0001.bin 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 at 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_0.5.3%2Bgit1-1_amd64.deb wget https://launchpad.net/~osmobuntu/+archive/ubuntu/ppa/+files/libosmocore_0.5.3%2Bgit1-1_amd64.deb 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/attachment.bin patch -p2 < attachment.bin make sudo ./simtrace Report success or failure to mxu at sanjole.com . From mxu at sanjole.com Tue Nov 18 21:40:52 2014 From: mxu at sanjole.com (mxu at sanjole.com) Date: Tue, 18 Nov 2014 11:40:52 -1000 (HST) Subject: Merging of Min Xu's patches In-Reply-To: <20141026165326.GM1197@nataraja> References: <20130809075847.GA4254@xiaoyu.lan> <20130824140553.GF16941@nataraja.gnumonks.org> <20130905073104.GG20992@nataraja.gnumonks.org> <20141026165326.GM1197@nataraja> Message-ID: <1416346852.212732077@apps.rackspace.com> Hi Harald Thank you so much for working on this. Since you have farmed out the formatting of the patches, and that I am less likely to have more time to work on this project, I am submitting all my git patches (11 of them so far) in a tgz format. I believe #1 to #6 were already sent in the past, #7 to #10 might have been sent to the mailing list, but I know #11 has not yet been sent to you or the mailing list. #1 to #10 were formatted as well as I could. #11 combined many changes and is not formatted as well. This is what my company currently use on all the board and we have not had any issues with it (GS5 / iPhone 6 / iPhone 5 etc). Maybe the person volunteering to split/format the changes will combine this in. Thank you so much. -----Original Message----- From: "Harald Welte" Sent: Sunday, October 26, 2014 6:53am To: "Min Xu" Cc: simtrace at lists.osmocom.org Subject: Merging of Min Xu's patches Dear Min Xu, Dear simtrace community, my sincere apologies for not getting around to merging your patches for what turned out to become more than a year. This is not intentional, but running a small company under constant overload left me with very little spare time and way too many neglected responsibilities towards the community projects :( I have finally taken some time to review, split/clean-up and merge the your patches. They are available in the 'minux-fixes' branch of openpcd.git, where the simtrace firmware is maitained for historical reasons. I didn't really (intend to) make any logical changes, but simply split it up in much smaller chunks, making sure that each patch really only addresses one issue, and also making sure that there are no unneeded whitespace changes in the change log. I have merged everything but the protocol change. For that, in order to have at least backwards compatibility from new host tools, we need to use the interfaceVersion as indicated by Peter Stuge earlier in this thread. I hope to be able to look at that before yet another year expires. If anyone wants to help out, I would appreciate patches for the following tasks: * forward-porting of min xu's protocol changes, but ** ensuring that the openpcd bulds still use the old protocol ** only simtrace builds should use the new protocol ** increment the bInterfaceVersion (for the simtrace builds only), once the change is made in the protocol * updating the simtrace host utility to check for bInterfaceVersion and provide code for both old and new protocol * ensure that changes to quantity and size of req_ctx apply only to simtrace builds, not to openpcd builds. Once all those issues are adressed, we can merge it into master. Please send a short message to this list if any of you is working on the above. p.s.: In other news, sysmocom has meanwhile produced and distributed close to 700 simtrace units. As it is a true open hardware project, we may not know how many others have built it themselves, using the schematics, bom and layout files provided. I would have never guessed that there are _that_ many people who have an interest in such an absolute 'niche' device. The only sad part is that despite that many users, we didn't get as many contributions. Neither on the wireshark dissector side, nor on the firmware side. Regards, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) -------------- next part -------------- A non-text attachment was scrubbed... Name: simtrace.gitpatches.tgz Type: application/x-compressed Size: 20306 bytes Desc: not available URL: