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 List,
Here are some bare-minimum code contributions for iso7816-3 slave side
protocol.
https://github.com/zwizwa/at91work/tree/apdu_phone
git@github.com:zwizwa/at91work.git
branch apdu_phone
Relevant files are in:
iso7816-slave-cdc-project/
src/
I spent a bit more time on this than expected on low-level platform
stuff, leaving me with no time to smooth the rough edges at the PC
interface side. It's a start, though.
Features:
- non-blocking iso7816-3 state machine for slave-side protocol
(reusable in COS?)
- low-level AT91 USART is abstracted as iso7816_port.h
- line-oriented ASCII HEX protocol over CDC USB serial, easy to use in
(python) scripts
- transport is separate from state machine, easy to replace with other
discussed mechanisms
- works for me on Nexus One and BLU SAMBA JR plus
Non-features:
- hardcoded ATR
- hardcoded power cycle skipping to select correct operating voltage
- not using SIMtrace SIM slot (see mim.py for using a PC card reader to
complete MITM)
- did not test with DFU but should work (I used Atmel SAM-ICE)
- standalone firmware, not integrated with CCID / sniffer
- git history is messy. i'd just flatten it for further work
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
Hi guys,
I'm thinking of making an application on top of simtrace, but my focus
would be on Windows users. I'd like to know if the application runs ok on
Windows systems.
--
Atenciosamente,
Hugo Frederico Soares
