Hi!
I really don't want to feel this list to be abused for advertisements,
but in this case I'm sure it is of actual help to a number of people on
this list:
The sysmocom web shop finally has a 3FF (micro-SIM) adapter cable
available: http://shop.sysmocom.de/products/simtrace-fpc-3ff
Please note that (as opposed to the regular mini-SIM) we only have one
of the possible four orientations available. This is primarily due to
the high manufacturing cost of low-volume flexible PCB projects.
We would like to hear from you
1) if you need this adapter in different orientation (which, for which
phone)
2) for which phone model you have used this new 3FF adapter successfully
3) what kind of problems you may have encountered using it.
Thanks to Kevin Redon for doing the PCB layout of this part. It is
freely available as part of the simtrace.git repository since commit
eee3243ddaa9e13bc7509a962fade8636b6ed2ab.
On a related note: For nanoSIM, I think we would have to go for
dual-layer PCB with vias placed inside the actual card contact pads.
This will make production cost even more expensive than the microSIM
adapter. So unless there's significant interest in a nanoSIM adapter,
it's unlikely that we'd have some made. Please let us know if you
absolutely want one, and if you're happy to pay even more (e.g. 25-30
EUR) for only that adapter.
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 List,
What is the current status of the MITM support? Anyone working on it
behind the scenes?
Also, I'd like to gauge how much work would be necessary to implement an
emulator mode, with emulator running on PC. I.e. SIMtrace used to doe
ATR handshake and then hand over all APDU to host PC over USB.
Cheers
Tom
Hi folks,
Seems not all phones use 3V signaling if the PHONE-side VCC pin is tied
to 3V.
This one insists on 1.8V : BLU SAMBA JR PLUS
Is this trick of tying VCC to 3V standard behavior?
For future version of the board, it might be interesting to tie the VCC
pin to an ADC input, to detect different voltage levels so the firmware
can wait until phone decides to use 3V.
Cheers
Tom
hello ,
anyone have schematic design sim reader PC/SC , yesterday i'm make
some reader but not support with PC/SC apps in here
(http://git.osmocom.org/osmo-sim-auth | A smart card reader compatible
with pcsc-lite) i think my card support with phoenix reader? and
anyone can explain the differences between the PC / SC with phoenix
sim reader or etc
Regards
Hi!
I have built 2 units of simtrace hardware recently. All the components came
from digikey, I used the bom list from git. The PCBs are electrically
tested.
When I connected it to the pc, simtrace application can communicate with
the device and I can debug it via the FTDI connection. The problem is, when
I connect it to a cellphone, cellphone can not detect a sim card. Simtrace
can detect vcc on, vcc off and rst signals from the cellphone however,
cellphone can not detect the sim card. I used several different cell phones
and sim cards. I also checked the connection between the cellhpone and
simtrace. Couldn't find a problem.
May I kindly request your help to solve the problem?
Thanks,
Hi List,
This might be of interest to folks here.
A couple of days ago I found out the Saleae Logichas an SDK that allows
you to live stream raw sample data straight into a C++ application.
Quite neat, as it can go to fairly high sample rates.
Here is a proof of concept version of a live APDU protocol sniffer using
the SL:
https://github.com/zwizwa/sl-apdu
Essentially it's just a UART state machine with some hardcoded ATR
parsing (for the specific SIM card I have) which calls into apdu_split
from git://git.osmocom.org/simtrace.git after the ATR handshake.
I had a look at the ISO7816 parser in the SIMtrace firmware, but it's
fairly tied to the hardware. With some refactoring it's probably easy
to reuse. ( The sl-apdu repo has a first attempt to a dirty stub
approach to run the original AT91 code. Probably not be the way to go.. )
Cheers
Tom
