From: Fabian Mewes <architekt@coding4coffee.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] openvpn: CVE-2014-8104: bump to version 2.3.6
Date: Mon, 1 Dec 2014 22:50:11 +0100 [thread overview]
Message-ID: <1417470611-27172-1-git-send-email-architekt@coding4coffee.org> (raw)
In-Reply-To: <547CDED0.9050305@zacarias.com.ar>
see
https://community.openvpn.net/openvpn/wiki/SecurityAnnouncement-97597e732b
Signed-off-by: Fabian Mewes <architekt@coding4coffee.org>
---
package/openvpn/openvpn.hash | 2 +-
package/openvpn/openvpn.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/openvpn/openvpn.hash b/package/openvpn/openvpn.hash
index 4e1911a..38579ab 100644
--- a/package/openvpn/openvpn.hash
+++ b/package/openvpn/openvpn.hash
@@ -1,2 +1,2 @@
# Locally calculated after checking pgp signature
-sha256 7ac286f09ed4981358ce01907993dc29f69b34d3652de2b70ca9b8b2a056b684 openvpn-2.3.5.tar.xz
+sha256 adae2ef34c9225347a844683b88caa87cde0979b7f2390fd1776db0eb51510ed openvpn-2.3.6.tar.xz
diff --git a/package/openvpn/openvpn.mk b/package/openvpn/openvpn.mk
index e0dba35..d9871ef 100644
--- a/package/openvpn/openvpn.mk
+++ b/package/openvpn/openvpn.mk
@@ -4,7 +4,7 @@
#
################################################################################
-OPENVPN_VERSION = 2.3.5
+OPENVPN_VERSION = 2.3.6
OPENVPN_SOURCE = openvpn-$(OPENVPN_VERSION).tar.xz
OPENVPN_SITE = http://swupdate.openvpn.net/community/releases
OPENVPN_DEPENDENCIES = host-pkgconf
--
1.7.10.4
next prev parent reply other threads:[~2014-12-01 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 21:26 [Buildroot] [PATCH] openvpn: CVE-2014-8104: bump to version 2.3.6 Fabian Mewes
2014-12-01 21:34 ` Gustavo Zacarias
2014-12-01 21:50 ` Fabian Mewes [this message]
2014-12-02 9:30 ` [Buildroot] [PATCH v2] " Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1417470611-27172-1-git-send-email-architekt@coding4coffee.org \
--to=architekt@coding4coffee.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox