Restore "openvpn@.service" from packaging of openvpn 2.3.6, so we can
start the sysmocom vpn the same way as currently described in the
Previous patch 8439e71a99 already
attempted to do this, but only brought back "openvpn.service" and not
Fixes: 8439e71a ("openvpn: bring back openvpn.service file")
Remove this directory to prepare to upgrade dropbear in following
patches. The directory made changes to the sysvinit script that was
used by pre-201705 systems (SYS#691). 201705 uses systemd services
On a side note, all customizations made to the init script had been
upstreamed into OE.
Package OpenSSH's sftp-server program, so we can install it as
dependency of dropbear in a future patch. Once sftp-server is installed,
the scp tool from OpenSSH can be used with the SFTP protocol, without
enabling the legacy flag for the legacy SCP protocol.
The sftp-server binary is 126K in size.
After packaging this, I realized that we could also have used
the openssh-sftp-server package from poky:
But let's use this extra package now, it uses the most recent OpenSSH
source and doesn't build the rest of OpenSSH which we don't need.
Adjust the bundled udev rules to use gpsd.hotplug instead of
gpsd.hotplug.wrapper, as the wrapper has been removed upstream.
systemd-udevd: failed to execute '/lib/udev/gpsd.hotplug.wrapper' '/lib/udev/gpsd.hotplug.wrapper': No such file or directory
Fixes: 6a8f914b ("gpsd: upgrade to 3.24")
Restore the openvpn.service file from packaging of openvpn 2.3.6, so we
can still start it the same way (as currently described in manuals).
Our openvpn server has meanwhile been migrated to 2.5.x, and
establishing backwards compatibility with 2.3.x means we have to
disable ciphers + tls versions that are no longer considered secure.
Usually when upgrading packages, we just copy the upstream package and
adjust it slightly. I've looked at the upstream package here:
(HEAD at f3d14d41ad60d2d52a0ea795ae10fe0882146ed1)
But as I compared both packaging trees, I found ours is quite different
than upstream. We have a lot of additional patches, still use python2 and
have these extra files:
│ ├── 60-gpsd.rules
│ ├── gpsd
│ ├── gpsd-default
│ ├── gpsd.service
│ ├── oc2g
│ │ ├── gpsd-default
│ │ └── gpsd.service
│ ├── sysmobts2100
│ │ └── gpsd-default
│ ├── sysmobts-v2
│ │ └── gpsd-default
│ └── sysmocom-idu
│ └── gpsd-default
Therefore I didn't start with the upstream packaging but instead
increased the gpsd version in our packaging and went through each patch
to see if it can be dropped or needs to be forward ported.
Change the version by renaming the .bb file. Reset the version of the
recipe (PR) back to "r0" again, as it is common practice after changing
the package version. The previous value "r3.20" looked a bit like a
package version, but it's not that.
* 0002-gps2udp-leave-argv-untouched.patch (leave-argv-untouched.patch)
* 0003-tsip-configure-and-enable-1PPS.patch (gpsd-tsip-pps.patch)
Add build fixes:
unused in previous version
doesn't apply, instead disable docs building via manbuild='no'
not needed anymore (no splintopts line in 3.24)
doesn't apply, not needed anymore (see 5df2de36 in gpsd.git)
Build osmo-bts and osmo-pcu from the tag instead of the commit, so we
don't need to update the commit. This is how it works in
Fixes: 9a554791 ("Update Osmocom recipes to latest tags (release 202302)")
Package sysmocom-openvpn-config was recently added to
task-sysmocom-tools. That task is pulled in by default into images. We
don't actually want that. Instead, we want the package to be available
in feeds, but without being installed into the image by default. Hence,
revert the recent commit and put the package in task-sysmocom-feed.bb
This reverts commit 34d053fbe8.
It was found that this patch (from 7 years ago) breaks upgrade path and
current behavior (user manual) of the sysmocom VPN.
It is expected that the systemd service openvpn.service is disabled by
default, and that the user simply has to enable/disable it to
enable/disable the sysmocom VPN.
This affects all images deployed until today, since until recently an
old sysmocom-openvpn-config package (from around 2013) was being used
during provisioning, instead of using the one we recently made available
into the regular 201705 feeds.
sysmocom-alix and sysmocom-apu2 are both based on sysmocom-bsc
Since we use those for the 3G starterkits add iu distro feature which
will install osmo-hnbgw and build osmo-msc and osmo-sgsn with iu