Hi all,
I'm thinking of starting a project that would allow us to
* perform SIM and USIM card pre-personalization
* read/dump and explore [U]SIM contents interactively
* perform SIM card simulation
The idea is to start with some generic data structure that can represent
the filesystem tree (DFs, EFs) and their "external" properties, i.e.
file type, size, permissions, FID, SFID, etc.
This data structure could also have the actual file content associated
with each EF.
The second step would be some code that can take that data structure and
program a freely-programmable card (like sysmoSIM-GR1) and create the
files according to that structure.
Another module would implement card-simulation (via BT SAP, SIMtrace or
virtual PC/SC card). After all, only a few instructions have to be
imilpemented if the filesystem and its content is already in a generic
data structure that the program can access..
Next step would be to associate parser and generator routines for the
content of each individual file as it is specified in TS 11.11.
After that has been done, we could think of representing the FS tree and
the parsed contents of each file in some kind of graphical / user
friendly representation. The idea here is that the UI code would be
generic and not know any of the actual ecnoding/decoding of the EF
content.
The biggest question is what language to use for this. Some kind of
object orientation might very well resemble the idea of a 'file object'
in a tree, with many different file types, each having it's own
parser/encoder.
On the other hand, Erlang's bit field syntax would probably come very
handy in terms of encoding/decoding the various EF content. However, at
least once we start to want some kidn of UI, Erlan really sucsk. Also,
almost nobody here reads/writes Erlang [yet?].
Writing all this in C seems like a bit much of an effort, probably even
more so on the UI side. However, we already have quite a bit of C code
for parsing/generating things like LAI, etc. which are stored like 04.08
inside the sim card files.
Python might be a good idea in terms of tons of available
libraries/modules, object orientation and good UI bindings. The biggest
problem here is that my python skills are really limited so far, so my
productivity might not be as high as I expect.
The individual components could even be written in different
languages, but then we would have to have some common format for
exchanging data back and forth - which might not be worth it, given the
small scope of the project.
any ideas / comments / feedback?
--
- 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)
From: Holger Hans Peter Freyther <zecke(a)selfish.org>
These address various compiler warnings, there is still one left
related the flash handling but I will need to read a bit more on
the EFC. I have flashed my device using DFU with these patches applied.
Holger Hans Peter Freyther (5):
dfu: The i variable to disable interrupts shadows the outer index
dfu: udp_ep0_recv_clean is static and is not called anywhere
dfu: Mark unsued variables as __unused for now
dfu: Use {} for possible empty if statement (in case debug is off)
dfu: Remove unused variable, mark method as not retuning
firmware/include/asm/compiler.h | 3 +++
firmware/src/dfu/dfu.c | 36 +++++++++++-------------------------
2 files changed, 14 insertions(+), 25 deletions(-)
--
1.7.7.2
Hi!
Thanks to Bjoern Kerler, we now have some bugfixes in fi/di calculation,
which apparently was broken for cerain newer phones like the HTC Raphael
or GT-S7070.
If you had any problems regarding PPS/PTS and higher baud rates of the
SIM card interface, feel free to try this new version. The source code
can be found in openpcd.git as usual.
Firmware can be installed into the application partition using dfu-util.
--
- 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)
Hi all,
I have updated the usermanual and provided a section on the Firmware itself
(getting, building, programming). This was written at night so I would be very
happy if someone could proof read or provide feedback in any other way.
I have moved some content in the Wiki as well, everything that is related to
Hardware should be in the Hardware article[2] and everything related to the
Firmware should be in the Firmware article[3]. I tried hard to not lose any
information. Again please take a look.
holger
[1] http://bb.osmocom.org/trac/raw-attachment/wiki/SIMtrace/usermanual.pdf
[2] http://bb.osmocom.org/trac/wiki/SIMtrace/Hardware
[3] http://bb.osmocom.org/trac/wiki/SIMtrace/Firmware
Hi
I tried SIMTrace with Gemalto java smart cards and it is working great.
Unfortunately I can’t run it on my shiny Mac OSX (Darwin Kernel Version 10.8.0), hosting Ubuntu in VMware.
SIMtrace is flashed with the latest firmware (see http://lists.osmocom.org/pipermail/simtrace/2011-August/000109.html)
If I connect it to my mac the red light is flashing periodically.
In the kernel log I see the following messages:
9/28/11 9:47:05 PM kernel USBF: 428978. 89 [0xadd3100] The IOUSBFamily was not able to enumerate a device.
9/28/11 9:47:06 PM kernel USBF: 428979.493 [0xadd3100] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 4 of Hub at 0x6000000)
9/28/11 9:47:06 PM kernel USBF: 428979.493 [0xadd3100] The IOUSBFamily was not able to enumerate a device.
9/28/11 9:47:07 PM kernel USBF: 428980.898 [0xadd3100] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 4 of Hub at 0x6000000)
9/28/11 9:47:07 PM kernel USBF: 428980.898 [0xadd3100] The IOUSBFamily was not able to enumerate a device.
9/28/11 9:47:09 PM kernel USBF: 428982.303 [0xadd3100] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 4 of Hub at 0x6000000)
....
with logging enabled:
9/29/11 9:10:33 PM kernel USBF: 1466.294 AppleUSBOHCI[0x7679000]::MakeDevice error setting address. err=0xe00002ed device=0x96d3400 - releasing device
9/29/11 9:10:33 PM kernel USBF: 1466.294 **5** AppleUSBHubPort[0x77d5c00]::AddDeviceResetChangeHandler - Port 4 of Hub at 0x6000000, unable to set device 0 to address 0 - disabling port
9/29/11 9:10:33 PM kernel USBF: 1466.296 AppleUSBHubPort[0x77d5c00]::DetachDevice Port 4 of Hub at 0x6000000 being detached (_attachRetry = 0)
9/29/11 9:10:33 PM kernel USBF: 1466.296 [0x77d5c00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 4 of Hub at 0x6000000)
9/29/11 9:10:33 PM kernel USBF: 1466.296 AppleUSBHubPort[0x77d5c00]::DetachDevice - Port 4 of Hub at 0x6000000 - device has gone away
9/29/11 9:10:33 PM kernel USBF: 1466.296 [0x77d5c00] The IOUSBFamily was not able to enumerate a device.
9/29/11 9:10:34 PM kernel USBF: 1467.700 AppleUSBOHCI[0x7679000]::MakeDevice error setting address. err=0xe00002ed device=0x96d3400 - releasing device
9/29/11 9:10:34 PM kernel USBF: 1467.700 **5** AppleUSBHubPort[0x77d5c00]::AddDeviceResetChangeHandler - Port 4 of Hub at 0x6000000, unable to set device 0 to address 0 - disabling port
9/29/11 9:10:34 PM kernel USBF: 1467.702 AppleUSBHubPort[0x77d5c00]::DetachDevice Port 4 of Hub at 0x6000000 being detached (_attachRetry = 0)
9/29/11 9:10:34 PM kernel USBF: 1467.702 [0x77d5c00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 4 of Hub at 0x6000000)
9/29/11 9:10:34 PM kernel USBF: 1467.702 AppleUSBHubPort[0x77d5c00]::DetachDevice - Port 4 of Hub at 0x6000000 - device has gone away
9/29/11 9:10:34 PM kernel USBF: 1467.702 [0x77d5c00] The IOUSBFamily was not able to enumerate a device.
9/29/11 9:10:36 PM kernel USBF: 1469.107 AppleUSBOHCI[0x7679000]::MakeDevice error setting address. err=0xe00002ed device=0x96d3400 - releasing device
9/29/11 9:10:36 PM kernel USBF: 1469.107 **5** AppleUSBHubPort[0x77d5c00]::AddDeviceResetChangeHandler - Port 4 of Hub at 0x6000000, unable to set device 0 to address 0 - disabling port
9/29/11 9:10:36 PM kernel USBF: 1469.109 AppleUSBHubPort[0x77d5c00]::DetachDevice Port 4 of Hub at 0x6000000 being detached (_attachRetry = 0)
9/29/11 9:10:36 PM kernel USBF: 1469.109 [0x77d5c00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 4 of Hub at 0x6000000)
9/29/11 9:10:36 PM kernel USBF: 1469.109 AppleUSBHubPort[0x77d5c00]::DetachDevice - Port 4 of Hub at 0x6000000 - device has gone away
9/29/11 9:10:36 PM kernel USBF: 1469.109 [0x77d5c00] The IOUSBFamily was not able to enumerate a device.
9/29/11 9:10:37 PM kernel USBF: 1470.512 AppleUSBOHCI[0x7679000]::MakeDevice error setting address. err=0xe00002ed device=0x96d3400 - releasing device
Please find attached also the trace logs form USBProber and usbtracer.
Any ideas how this could be fixed?
Ben
Hi all,
we have accumulated a number of wireshark patches, and by far not all of
them have been merged into mainline wireshark so far (volunteers, anyone?)
Some people have complained that it is hard to build them, as you first
have to find a wireshark version to which they apply, etc.
We have now created a wireshark.git repository at git.osmocom.org in
which you will be able to find the latest mainline wireshark version
('trunk' branch) as well as our patches in 'master':
http://cgit.osmocom.org/cgit/wireshark/
the read-onIy clone url is 'git://git.osmocom.org/wireshark'
So the recommended option for everyone needing patched wireshark for one
or the other reason (e.g. simtrace) now is to clone that wireshark.git
repository and build from there.
Like before, we will rebase our patches in irregular intervals, so you
may have to do a 'pull -f' instead of 'pull' at that time.
Regards,
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)
Hi all,
it's now something like two weeks after the first 60 or so SIMtrace kits
have been sold - but remarkably quite in here.
I've been busy with mostly non-technical stuff, so I couldn't spend any
more time improving the firmware/software.
However, at least some of the SIMtrace owners should have used the
device until now and gathered some data and/or experience. Please feel
free to share your progress or problems here, including topics like
* firmware update
* simtrace host software
* wireshark dissector
Regards,
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)
Hi all,
at the CCC Camp two weeks ago, a Chinese guy approached me, stating that
there he has contacts to a considerable supply of very inexpensive C1xx
family phones in China.
Unfortunately we didn't exchange contact details, so I'm trying this
route. If you are the person that has talked to me about this topic,
pleaes contact me by private e-mail.
I would love to use this opportunity to provide inexpensive C1xx phones
to the larger OsmocomBB user community.
Thanks in advance,
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)
Hi all,
I have toyed with spreecommerce[1] on and off and would like to have some
friendly users to see if the whole checkout process is working. The shop can
be found here[2] but I would like to share some technical details with you.
My patched spreecommerce can be found on gitorious[3], for some of the changes
I should have created an extension but right now I think I prefer git pull
--rebase to see what changed. If you enter your EUVAT number you should not be
charged VAT (unless you are in Germany).
We are using a CA Cert signed certificate, your browser will tell you that it
is dangerous, I think we prefer putting the money into future HW products than
getting a signature from a 'trust worthy' org.
Shipping cost calculation is a bit of a mess, does anyone know if DHL offers
an API for it? The installation has four zones (Germany, EUVAT region, USA,
World Wide)?
Terms/Conditions and Privacy Policy are very basic and need to be refined,
with best effort I tried to make short and clear.
Technical feedback, specially on caching, rails (security), etc. is very welcome.
holger
[1] spreecommerce.com
[2] https://shop.sysmocom.de
[3] https://gitorious.org/sysmocom-spreecommerce
Hi,
I just wanted to ask for a short heads up of the release schedule. I know
you have been selling the boards at the CCC camp, but I haven't been
there. It was mentioned on the list that you are planning to sell it
through a web shop in the "2nd half of august".
I am sorry for being in such a hurry, but I'd really like to have the
boards on my desk in august, due to my holidays afterwards.
Cheers,
Dirk