similarity index 47%
rename from meta-networking/recipes-support/openvpn/openvpn_2.6.3.bb
rename to meta-networking/recipes-support/openvpn/openvpn_2.6.6.bb
@@ -1,8 +1,75 @@
+# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'.
+# The following is the difference between the old and the new license text.
+# Please update the LICENSE value if needed, and summarize the changes in
+# the commit message via 'License-Update:' tag.
+# (example: 'License-Update: copyright years updated.')
+#
+# The changes:
+#
+# --- COPYING
+# +++ COPYING
+# @@ -30,6 +30,53 @@
+# this file, you may extend this exception to your version of the
+# file, but you are not obligated to do so. If you do not wish to
+# do so, delete this exception statement from your version.
+# +
+# +Apache2 linking exception:
+# +---------------------------
+# +OpenVPN is currently undergoing a license change to add an exception for
+# +Apache 2 linking. The following exception is only valid for new contributions
+# +after 2023-05-03 and past contribution where the authors have already agreed
+# +to the exception.
+# +
+# + In addition, as a special exception, OpenVPN Inc and the
+# + contributors give permission to link the code of this program to
+# + libraries (the "Libraries") licensed under the Apache License
+# + version 2.0 (this work and any linked library the "Combined Work")
+# + and copy and distribute the Combined Work without an obligation to
+# + license the Libraries under the GNU General Public License v2
+# + (GPL-2.0) as required by Section 2 of the GPL-2.0, and without an
+# + obligation to refrain from imposing any additional restrictions in
+# + the Apache License version 2 that are not in the GPL-2.0, as
+# + required by Section 6 of the GPL-2.0. You must comply with the
+# + GPL-2.0 in all other respects for the Combined Work, including
+# + the obligation to provide source code. If you modify this file, you
+# + may extend this exception to your version of the file, but you are
+# + not obligated to do so. If you do not wish to do so, delete this
+# + exception statement from your version.
+# +
+# +For better understanding, in plain non-legalese English this basically says:
+# +
+# + * The intention for this license exception is to allow OpenVPN to be
+# + linked against APL-2 licensed libraries, even where the GPL-2.0 and
+# + APL-2 licenses conflict from a legal perspective.
+# +
+# + * OpenVPN itself will stay GPL-2.0 and the code belonging to the
+# + OpenVPN project must comply to the GPL-2.0 license. This is NOT
+# + dual-licensing of the OpenVPN code base.
+# +
+# + * This license exception DOES NOT require NOR expect a license change
+# + of the APL-2 based library. This exception allows using the APL-2
+# + library as-is. However, when distributing a compiled OpenVPN binary
+# + linking against APL-2 libraries ("Combined Work"), the REQUIREMENT is
+# + that the APL-2 library MUST also be available on similar terms as in
+# + GPL-2.0, like providing the source code of the library upon request,
+# + except in the two specific ways mentioned.
+# +
+# + * If the APL-2 based library forbids such linking and distribution,
+# + this license exception DOES NOT overrule the restriction of the APL-2
+# + based library. If the APL-2 library cannot satisfy the requirements
+# + in this license exception, you CANNOT distribute an OpenVPN binary
+# + linked with this library.
+#
+# LZO license:
+# ------------
+#
+#
+
SUMMARY = "A full-featured SSL VPN solution via tun device."
HOMEPAGE = "https://openvpn.net/"
SECTION = "net"
LICENSE = "GPL-2.0-only"
-LIC_FILES_CHKSUM = "file://COPYING;md5=3170e982baae61dbb8de963317d1ac94"
+LIC_FILES_CHKSUM = "file://COPYING;md5=d8d34ce6390552676e4ce8279f13c48a"
DEPENDS = "lzo lz4 openssl iproute2 libcap-ng ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}"
inherit autotools systemd update-rc.d pkgconfig
@@ -14,7 +81,7 @@ SRC_URI = "http://swupdate.openvpn.org/community/releases/${BP}.tar.gz \
UPSTREAM_CHECK_URI = "https://openvpn.net/community-downloads"
-SRC_URI[sha256sum] = "13b207a376d8880507c74ff78aabc3778a9da47c89f1e247dcee3c7237138ff6"
+SRC_URI[sha256sum] = "3b074f392818b31aa529b84f76e8b5e4ad03fca764924f46d906bceaaf421034"
CVE_STATUS[CVE-2020-27569] = "not-applicable-config: Applies only Aviatrix OpenVPN client, not openvpn"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *openvpn* to *2.6.6* has Succeeded. Next steps: - apply the patch: git am 0001-openvpn-upgrade-2.6.3-2.6.6.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From c108569fe2e9d2c7e341273cc6ca7a9e51944056 Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Sat, 4 Nov 2023 02:46:06 +0000 Subject: [PATCH] openvpn: upgrade 2.6.3 -> 2.6.6 --- .../{openvpn_2.6.3.bb => openvpn_2.6.6.bb} | 71 ++++++++++++++++++- 1 file changed, 69 insertions(+), 2 deletions(-) rename meta-networking/recipes-support/openvpn/{openvpn_2.6.3.bb => openvpn_2.6.6.bb} (47%)