Dear Sir or Madam: I've bought two simtrace development boards two months ago in order to research the communication between the SIM-card and the mobile phone. However, recently when I need to analyse the packet which contains CK and IK, I sadly found that the packet was not captured every time. Mostly it returns as a malformed packet in the wireshark, which blocks my future studying. I read the user manual and it says that for some high speed cards the firmware can lose bytes, and to solve that we can reduce the size of the buffer. So I'm writing to ask the specific steps to reduce the buffer and recompile the firmware, and I've tried by myself but I couldn't find a proper toolchain which includes a GCC but not an EABI. I'm looking forward to your reply. Best wishes! Yours, sincerely Luna-Qi
AFAIR the wireshark dissector only knows about the SIM RUN GSM ALGORITHM APDU format (with Kc), but not the USIM AUTHENTICATE APDU format (with CK and IK). https://github.com/wireshark/wireshark/blob/master/epan/dissectors/packet-gs... This is why it should always return a malformed packet (due to the dissector decoder). Did you check if the raw bytes actually match the USIM APDU and include CK+IK, or are bytes also missing there?
On Tue, Dec 13, 2016 at 09:22:13PM +0800, joranglequeen@sina.com wrote:
Dear Sir or Madam: I've bought two simtrace development boards two months ago in order to research the communication between the SIM-card and the mobile phone. However, recently when I need to analyse the packet which contains CK and IK, I sadly found that the packet was not captured every time. Mostly it returns as a malformed packet in the wireshark, which blocks my future studying. I read the user manual and it says that for some high speed cards the firmware can lose bytes, and to solve that we can reduce the size of the buffer. So I'm writing to ask the specific steps to reduce the buffer and recompile the firmware, and I've tried by myself but I couldn't find a proper toolchain which includes a GCC but not an EABI. I'm looking forward to your reply. Best wishes! Yours, sincerely Luna-Qi
Hi Kevin,
On Tue, Dec 13, 2016 at 08:08:41PM +0100, ml@mail.tsaitgaist.info wrote:
AFAIR the wireshark dissector only knows about the SIM RUN GSM ALGORITHM APDU format (with Kc), but not the USIM AUTHENTICATE APDU format (with CK and IK).
yes, this is true. I can only re-iterate that Osmocom SIMtrace, just like wreshark, are community-based collaborative Free Software development projects, and they will always only support whatever somebody decides to contribute in terms of code.
Every user would be more than happy if somebody implemented dissection of USIM/UICC, or even dissection of the actual EF content [which is of course different for each EF].
The existing GSM SIM dissector was the minimal posible useful set that I could implement at the time. Unfortuantely, nobody seems to have followed up in all those years, except for Pascal Quentin with some much appreciated SIM Toolkit related work.
So everyone at that list: Each time you see something missing, please take some time to implement it. Only that way collaborative software development projects are stustainable. Thanks for your understanding.
Kevin and I certainly did our part to get SIMtrace off the ground many years ago in terms of hardware, firmware and the existing application code / wiershark code. If you're reading this: Now it's your turn, pleaes help make the project better and more complete. Thanks!
Regards, Harald
Hi Luna
I am not sure why this question is still coming up. I am under the impression that git already includes my changes, which I believe already resolves buffering issues. I have no issues reading CK/IK commands (although I do recommend you to use your own parser as I think wireshark parser is very limited) on any 3G/4G sim cards.
You should be able to find a binary build of the changes I made in an earlier email I submited. However, do take note that the client application will have to be changed as well because additional fields had to be added to the usb packet header)
Best regards
On Tue, Dec 13, 2016 at 3:32 AM, simtrace-request@lists.osmocom.org wrote:
---------- Forwarded message ---------- From: joranglequeen@sina.com To: simtrace simtrace@lists.osmocom.org Cc: Date: Tue, 13 Dec 2016 21:22:13 +0800 Subject: Some Questions about Simtrace Dear Sir or Madam: I've bought two simtrace development boards two months ago in order to research the communication between the SIM-card and the mobile phone. However, recently when I need to analyse the packet which contains CK and IK, I sadly found that the packet was not captured every time. Mostly it returns as a malformed packet in the wireshark, which blocks my future studying. I read the user manual and it says that for some high speed cards the firmware can lose bytes, and to solve that we can reduce the size of the buffer. So I'm writing to ask the specific steps to reduce the buffer and recompile the firmware, and I've tried by myself but I couldn't find a proper toolchain which includes a GCC but not an EABI. I'm looking forward to your reply. Best wishes! Yours, sincerely Luna-Qi
simtrace mailing list simtrace@lists.osmocom.org https://lists.osmocom.org/mailman/listinfo/simtrace
-
Harald Welte -
joranglequeen＠sina.com -
Min Xu -
ml＠mail.tsaitgaist.info