From laforge at gnumonks.org  Sun Oct  1 02:00:17 2017
From: laforge at gnumonks.org (Harald Welte)
Date: Sun, 1 Oct 2017 10:00:17 +0800
Subject: simtrace as a remote sim solution
In-Reply-To: <74a7e93e-315d-8cdf-5869-d81eb27df869@uhusystems.com>
References: <74a7e93e-315d-8cdf-5869-d81eb27df869@uhusystems.com>
Message-ID: <20171001020017.jsumtnpjfrygybmh@nataraja>

Hi Balazs,

your e-mail was in the moderator queue for more than a month, my apologies for this.

It's a members only list and I guess we don't have that many non-member posts
on this list so it gets looked at only very infrequently

On Tue, Aug 15, 2017 at 10:59:30PM +0200, pozsy at uhulinux.hu wrote:

> Just found this project which seems to be quite interesting to me. Tried to
> read through all the information on the project page before asking, but not
> everything is clear yet :)
> 
> So what I would like to achieve is basically the man-in-the-middle (mitm)
> mode. I do not actually need to modify any communication on its way, all I
> would like to do is to have:
> a) the sim card in a reader connected to host (A), while
> b) the gsm module is connected to an other host (B)
> and relaying their communication back and forth through some IP network.

This is supported in the simtrace2.git firmware tree, which unfortunately
still only works with the sysmoQMOD board at this point.  It's on the todo
list to port this to a new simtrace board version with a SAM3 microcontroller,
and not the old SAM7 as on the existing simtrace boards.  But given my limited
spare time and many projects, this has not yet been a priority :/

> I guess I would need two pieces of simtrace hardware for that, 

Actually, only one.  The card reader is a standard card reader supported by pcsc_lite attached
to a Linux machine. A proof-of-concept host utility is provided in the "host" subdirectory,
see https://git.osmocom.org/simtrace2/tree/host

> - Do you think this could work with the current hw/fw design?

simtrace2.git firmware *could* be ported to the old SAM7 based hardware, but it
would be a significant porting effort.  The advantage of the new SAM3 based design
is that the processor is much more powerful, and that it supports more USB endpoints,
so that we can expose a USB-CCID compliant card reader device for the SIM slot at
the same time as we can export the "sim card emulation" part towards the phone/modem.

This is of course only relevant if you want to do local MITM, with no network in
between.

> - What would be the maximum network delay allowed?

Completely uncriticial.  In fact, the card emulation code of the firmware
(see https://git.osmocom.org/simtrace2/tree/firmware/libcommon/source/card_emu.c)
implements waiting time extension as per ISO7816-3 if the answer from the remote
card (or host PC) takes longer than expected.

In the real world, what's most critical is the authentication requests.  As far as
I remember, about four seconds are acceptable for the authentication procedure as per the default timers
specified for the VLR/MSC in the GSM specs.

> - Do you know of any alternative solutions for my needs?

see above.

> ps: I would also be willing to pay for professional consultancy services on
> this topic.

sysmocom can provide any related engineering/development/consulting services,
but by all means we don't want to discourage others to provide related services,
too.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From GNUtoo at no-log.org  Wed Oct  4 12:18:43 2017
From: GNUtoo at no-log.org (Denis 'GNUtoo' Carikli)
Date: Wed,  4 Oct 2017 14:18:43 +0200
Subject: [PATCH] firmware: Makefiles: enable changing toolchain
Message-ID: <20171004121843.5280-1-GNUtoo@no-log.org>

Without that the user was expected to either patch
the Makefiles or to get a toolchain with the arm-elf-
prefix.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo at no-log.org>
---
 firmware/Makefile     | 13 +++++++------
 firmware/Makefile.dfu | 13 +++++++------
 2 files changed, 14 insertions(+), 12 deletions(-)

diff --git a/firmware/Makefile b/firmware/Makefile
index 350b0dc..1581a1f 100644
--- a/firmware/Makefile
+++ b/firmware/Makefile
@@ -352,12 +352,13 @@ LPC21ISP_CONTROL = -control
 
 # Define programs and commands.
 SHELL = sh
-CC = arm-elf-gcc
-CPP = arm-elf-g++
-OBJCOPY = arm-elf-objcopy
-OBJDUMP = arm-elf-objdump
-SIZE = arm-elf-size
-NM = arm-elf-nm
+CROSS_COMPILE ?= arm-elf-
+CC = $(CROSS_COMPILE)gcc
+CPP = $(CROSS_COMPILE)g++
+OBJCOPY = $(CROSS_COMPILE)objcopy
+OBJDUMP = $(CROSS_COMPILE)objdump
+SIZE = $(CROSS_COMPILE)size
+NM = $(CROSS_COMPILE)nm
 REMOVE = rm -f
 COPY = cp
 
diff --git a/firmware/Makefile.dfu b/firmware/Makefile.dfu
index 3c797ef..1e9e71c 100644
--- a/firmware/Makefile.dfu
+++ b/firmware/Makefile.dfu
@@ -303,12 +303,13 @@ LPC21ISP_CONTROL = -control
 
 # Define programs and commands.
 SHELL = sh
-CC = arm-elf-gcc
-CPP = arm-elf-g++
-OBJCOPY = arm-elf-objcopy
-OBJDUMP = arm-elf-objdump
-SIZE = arm-elf-size
-NM = arm-elf-nm
+CROSS_COMPILE ?= arm-elf-
+CC = $(CROSS_COMPILE)gcc
+CPP = $(CROSS_COMPILE)g++
+OBJCOPY = $(CROSS_COMPILE)objcopy
+OBJDUMP = $(CROSS_COMPILE)objdump
+SIZE = $(CROSS_COMPILE)size
+NM = $(CROSS_COMPILE)nm
 REMOVE = rm -f
 COPY = cp
 
-- 
2.14.1



From laforge at gnumonks.org  Thu Oct  5 01:28:52 2017
From: laforge at gnumonks.org (Harald Welte)
Date: Thu, 5 Oct 2017 09:28:52 +0800
Subject: [PATCH] firmware: Makefiles: enable changing toolchain
In-Reply-To: <20171004121843.5280-1-GNUtoo@no-log.org>
References: <20171004121843.5280-1-GNUtoo@no-log.org>
Message-ID: <20171005012852.rvcwcsh5pjrpr3rl@nataraja>

On Wed, Oct 04, 2017 at 02:18:43PM +0200, Denis 'GNUtoo' Carikli wrote:
> Without that the user was expected to either patch
> the Makefiles or to get a toolchain with the arm-elf-
> prefix.

Thanks, I pushed this to gerrit, which is the preferred way of
code contributions in Osmocom now, see
https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit#Setting-up-Gerrit-for-commits-and-pushing

Your patch now lives at https://gerrit.osmocom.org/#/c/4140/

Regards,
	Harald

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From laforge at gnumonks.org  Sat Oct 14 06:01:40 2017
From: laforge at gnumonks.org (Harald Welte)
Date: Sat, 14 Oct 2017 08:01:40 +0200
Subject: Planning for OsmoCon + OsmoDevCon
Message-ID: <20171014060140.khxczgit4pe2icuq@nataraja>

[cross-post to many lists, please follow-up-to openbsc at lists.osmocom.org]

Dear all,

time is flying, and I would like to start early with discussions and planning
about OsmoCon and OsmoDevCon in 2018.  It helps to start early.

Side note: We have some pending issues about the events from last year at
http://osmocom.org/projects/osmo-dev-con/issues - I've incorporated them
in the text below.


== OsmoDevCon ==

For OsmoDevCon, I think it's easy: We keep it as-is.  Same procedure as
every year, which means:
* same venue, same catering options
* same concept of 'anyone contributing to Osmocom can apply for
  registration until all seats are taken'
* same idea of inviting some few speaker[s] doing other FOSS mobile
  communications work to join us

The parts that we need to change, IMHO:

* don't reduce from 4 to 3 days like last year. Have full 4 days again
* sort topics per day / half-day, i.e. have "GSM/UMTS Cellular
  Infrastructure" days for BTS/BSC/NITB/MSC/HLR/SGSN/GGSN & Co,
  but then have other days for other projects.  This would enable people
  not interested in the [continued evolvement] of the cellular projects
  be able to skip those days, or to simply meet in an adjacent room for
  parallel hacking sessions/discussions
* try to be a bit more structured with the schedule in general. The
  existing approach works for people who attend all the event all day
  long, but not so well for people with other plans / limited time

Any further change requests or topics to discuss?

Please note that Pablo Neira has offered to kindly host an OsmoDevCon in
Seville (Spain).  I've attended a number of netfilter workshops he
organized there, and he's doing a great job!  However, given the large
number of attendees from Berlin (and Germany in general), I think this
would make things more complicated, and more expensive for most
attendees.  If you disagree with that assessment: I'm open for having
the discussion, I just thought it's more practical/economic to do it in
Berlin.

=== 10 year Anniversary Party ===

Given that 2018 marks the 10 year anniversary of Dieter and me hacking
with the Siemens BS-11 in 2008, I think the 2018 incarnation deserves
some special celebration of some form.  I have no concrete idea yet, but
for sure we should so something, and it should be at/around
OsmoDevCon.  And for sure we should have a BS-11 around :)


== OsmoCon ==

The public OsmoCon was welcomed and was a success.  However,
let's start this discussion with a review of last years event.

=== Registration ===

* Registrations came in way too late. Two weeks ahead of the event, we were
  considering to cancel it.  And then within the last few days, we had
  to turn people down due to limited seating capacity

* To make planning more reliable, we see on other option but to
  significantly raise the registration fee combined with an equally
  significant discount for early booking

=== Duration ===

* Many people requested multiple days rather than just one, in order to
  make more out of (long distance) travels.  This is obvious, but as we
  had no idea how many people would attend at all (or if we have to
  cancel due to lack of attendance), planning multiple days in the first
  incarnation would have been high risk and a multitude of work

* I would suggest to expand to two or even three days this week,
  possibly one days with tutorials and the other day with tech talks

* Slightly less crammed schedule due to multiple days

=== Venue ===

We recognize this yearso venue was not the best option, due to
* Bad ventilation in the basemenet
* Difficult to find
* No space next to the conference room where people can meet / hang out
  in parallel to talks (not everyone attends every talk)

I still like the "understatement" of the venue.  I'd prefer any hostel /
non-profit / hackerspace / university over luxurious hotels any time.
Going to an expensive venue means more or less automatically more
expensive ticket fees, which again is more likely to exclude pure
community members without a commercial activity related to Osmocom.

So any future venue would ideally:

* be able to hold slightly more people than this year
* have a second room or large lobby in which people can meet for
  extended coffee breaks in parallel to some talks, as needed
* be slightly easier to find (and we have to put up some signs outside
  and in the lobby)
* have better WiFi and/or wired connectivity

=== Programme / Format ===

* less crammed over multiple days
* some more "interactive" formats were requested, for users to provide
  feedback to developers
* there was some discussion about topics / speakers in redmine last
  year, but not too much participation [until it was too late].
* I'd suggest a more formal CfP process with a submission deadline that
  allows us to publish a preliminary schedule long ahead of the event

=== Video Recordings ===

I think they were a big success, and it was a very big surprise that the
CCC Video Operations Center was volunteering to help such a small and
niche-interest event like OsmoCon.  We should make sure that we can
repeat this for 2018.


== Dates / Frequency ==

Having OsmoCon and OsmoDevCon back to back becomes somewhat long, if
OsmoCon is 2-3 days and OsmoDevCon is 4 days. Basically we're looking at
a full week for those of you who would like to attend both events.  But
then, I think the number of people attending both events is actually not
all that big.  Without checking the details, I think not more than half
of the OsmoDevCon attendees were attending OsmoCon.  I would expect that
tendency to remain or even increase.

I still think it's good to keep them back-to-back.

In terms of frequency,  I would actually suggest we move to a 6-month
cycle rather than a 12-month cycle.  There's a lot of development going
on at all time. I understand that not everyone is able to attend two
events just on Osmocom, especially if it's a spare time / hobby type
activity.  That's ok, I think there's no problem with attending either
of the two only, and catching up by video recordings and/or mail on the
other.

The qeustion is: Should that second event be developer-oriented or
user-oriented?  Or again both?  Any comments here?


Ok, that was a somewhat lengthy e-mail.  Please make sure to provide any
feedback you may have as early as possible, to increase the chances of
your feedback being reflected in the planning.

Happy hacking,
	Harald

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From achechet at gmail.com  Wed Oct 25 14:40:16 2017
From: achechet at gmail.com (Ale Ch)
Date: Wed, 25 Oct 2017 17:40:16 +0300
Subject: can't open USB device
Message-ID: <CAOx8V6iWF506BhRj6_fmz+xTNyOk4ZA-UfHye9t9ohqNp2E8gw@mail.gmail.com>

Dear collegues,
could you help me to start using SIMtrace board?
I have bought SIMtrace board v1.4 from symocom shop.

I have got sources from github but cannot (it is strange) built user manual
on my ubuntu computer.

BUT
I am successfully built simtrace application but it cannot recognize the
board.

>user at lnkd149:~/OSMOCOM/simtrace/host$ ./simtrace
>simtrace - GSM SIM and smartcard tracing
>(C) 2010 by Harald Welte <laforge at gnumonks.org>
>
>can't open USB device

that message I have received on my screen...
Could you advise something?

regards
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/simtrace/attachments/20171025/12ec6a79/attachment.htm>

From holger at freyther.de  Thu Oct 26 04:44:52 2017
From: holger at freyther.de (Holger Freyther)
Date: Thu, 26 Oct 2017 12:44:52 +0800
Subject: can't open USB device
In-Reply-To: <CAOx8V6iWF506BhRj6_fmz+xTNyOk4ZA-UfHye9t9ohqNp2E8gw@mail.gmail.com>
References: <CAOx8V6iWF506BhRj6_fmz+xTNyOk4ZA-UfHye9t9ohqNp2E8gw@mail.gmail.com>
Message-ID: <71CCE090-DAF9-4E4D-B42A-2F45547AB016@freyther.de>


> On 25. Oct 2017, at 22:40, Ale Ch <achechet at gmail.com> wrote:
> 

Hey,


> Dear collegues, 
> could you help me to start using SIMtrace board?
> I have bought SIMtrace board v1.4 from symocom shop.
> 
> I have got sources from github but cannot (it is strange) built user manual on my ubuntu computer.
> 
> BUT 
> I am successfully built simtrace application but it cannot recognize the board.


* The board was most likely coming with Firmware pre-installed
* The manual. I think you can download a copy attached to the wiki?
* What does not "recognized" mean?

holger

From achechet at gmail.com  Thu Oct 26 08:22:51 2017
From: achechet at gmail.com (Ale Ch)
Date: Thu, 26 Oct 2017 11:22:51 +0300
Subject: can't open USB device
In-Reply-To: <71CCE090-DAF9-4E4D-B42A-2F45547AB016@freyther.de>
References: <CAOx8V6iWF506BhRj6_fmz+xTNyOk4ZA-UfHye9t9ohqNp2E8gw@mail.gmail.com>
 <71CCE090-DAF9-4E4D-B42A-2F45547AB016@freyther.de>
Message-ID: <CAOx8V6jzw+F7RJ6A3r55t-2_bu86-KE2wOY6+E-65p7xR_uW7A@mail.gmail.com>

Dear Collegues!
I still never studied how to answer to maillist all of you, so send you
letter personaly:
Thank you a lot for your support and advices.
Now I have found my mistake.
I have never re-login-ed....

regards
Alex

2017-10-26 7:44 GMT+03:00 Holger Freyther <holger at freyther.de>:

>
> > On 25. Oct 2017, at 22:40, Ale Ch <achechet at gmail.com> wrote:
> >
>
> Hey,
>
>
> > Dear collegues,
> > could you help me to start using SIMtrace board?
> > I have bought SIMtrace board v1.4 from symocom shop.
> >
> > I have got sources from github but cannot (it is strange) built user
> manual on my ubuntu computer.
> >
> > BUT
> > I am successfully built simtrace application but it cannot recognize the
> board.
>
>
> * The board was most likely coming with Firmware pre-installed
> * The manual. I think you can download a copy attached to the wiki?
> * What does not "recognized" mean?
>
> holger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/simtrace/attachments/20171026/15305158/attachment.htm>

From achechet at gmail.com  Tue Oct 31 08:32:01 2017
From: achechet at gmail.com (Ale Ch)
Date: Tue, 31 Oct 2017 11:32:01 +0300
Subject: new APDU command - how?
Message-ID: <CAOx8V6ggXYDE1RVsi3G+adViYXB6N5pKw8akiZxMSROFKqYF9g@mail.gmail.com>

Hi!
Tell me please, how to add new APDU command discription to see it in
Wireshak log?
Where in source code lay this command description?

regards
Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/simtrace/attachments/20171031/2b9ea43d/attachment.htm>

From laforge at gnumonks.org  Tue Oct 31 09:28:46 2017
From: laforge at gnumonks.org (Harald Welte)
Date: Tue, 31 Oct 2017 10:28:46 +0100
Subject: new APDU command - how?
In-Reply-To: <CAOx8V6ggXYDE1RVsi3G+adViYXB6N5pKw8akiZxMSROFKqYF9g@mail.gmail.com>
References: <CAOx8V6ggXYDE1RVsi3G+adViYXB6N5pKw8akiZxMSROFKqYF9g@mail.gmail.com>
Message-ID: <20171031092846.5v7ew6revuaqt6xr@nataraja>

Hi Alex,

On Tue, Oct 31, 2017 at 11:32:01AM +0300, Ale Ch wrote:
> Tell me please, how to add new APDU command discription to see it in
> Wireshak log?
> Where in source code lay this command description?

You can find the current dissector in epan/dissectors/packet-gsm_sim.c

Please do contribute back any extensions you make, either directly to
the wireshark gerrit, or here, if you prefer that.  Thanks in advance for your
contribution.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)


From hwelte at sysmocom.de  Tue Oct 31 18:56:00 2017
From: hwelte at sysmocom.de (Harald Welte)
Date: Tue, 31 Oct 2017 19:56:00 +0100
Subject: Want to do paid work on Osmocom? sysmocom is hiring
Message-ID: <20171031185600.ca6izqakkcvg43nu@nataraja>

Dear Osmocom community,

I would like to point out that at sysmocom, we're currently (again)
hiring [1].  If you happen to have an interest in open source cellular
communications and are fluent in C language development, we would
love to hear from you.

sysmocom probably doesn't need any introduction here, but just in case:
The company was founded by Holger Freyther and Harald Welte, two of the
leading OpenBSC and Osmocom developers from the very early days of the
project.  Today we are responsible for by far the largest number of commits
to the Osmocom GSM/3G infrastructure related git repositories.

Among our current priorities are automatic testing for the GPRS PCU,
generalization of the OsmoMGW media gateway, support for load-based hand-over,
inter-BSC hand-over as well as various improvements on the lower layers
of the GPRS protocol stack.

We're very dedicated to the cause in furthering the capabilities of
open source cellular infrastructure from 2G to 4G.  We believe in
working upstream, no open core or dual licensing.

If you have an interest working with an enthusiastic, strong technical
and dedicated team of Osmocom hackers, please don't hesitate to let me know,
best by e-mail to jobs at sysmocom.de

Thanks,
	Harald

p.s.: I hope this kind of message is not disturbing to anyone.  I think
it is important to the Osmocom project to have more paid people working
on the stack, so it is justified.  The positions we are seeking to fill
will work [almost exclusively] on Osmocom, so it's not a random job ad
but in the very interest of Osmocom, and hence on-topic for this list.

[1] https://www.sysmocom.de/jobs/

-- 
- Harald Welte <hwelte at sysmocom.de>             http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte