From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. c3e195433152f91a3f14d59d6ea10e8963e6308d
Date: Fri, 12 Jun 2015 17:17:06 +0200 [thread overview]
Message-ID: <20150612151706.A798F221D0@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3302 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, master has been updated
via c3e195433152f91a3f14d59d6ea10e8963e6308d (commit)
from 6646be5a53c2fa4846f6403d887a2975469800f6 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit c3e195433152f91a3f14d59d6ea10e8963e6308d
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Jun 12 17:15:51 2015 +0200
strongswan: Update to 5.3.2
This release fixes a security issue filed under CVE-2015-4171.
https://www.strongswan.org/blog/2015/06/08/strongswan-vulnerability-(cve-2015-4171).html
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/strongswan | 6 ++----
src/patches/strongswan-5.3.1-build-timeattack.patch | 11 -----------
2 files changed, 2 insertions(+), 15 deletions(-)
delete mode 100644 src/patches/strongswan-5.3.1-build-timeattack.patch
Difference in files:
diff --git a/lfs/strongswan b/lfs/strongswan
index d1a5b8c..b4438dd 100644
--- a/lfs/strongswan
+++ b/lfs/strongswan
@@ -24,7 +24,7 @@
include Config
-VER = 5.3.1
+VER = 5.3.2
THISAPP = strongswan-$(VER)
DL_FILE = $(THISAPP).tar.bz2
@@ -48,7 +48,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 66f258901a3d6c271da1a0c7fb3e5013
+$(DL_FILE)_MD5 = fab014be1477ef4ebf9a765e10f8802c
install : $(TARGET)
@@ -78,10 +78,8 @@ $(subst %,%_MD5,$(objects)) :
$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
- cd $(DIR_APP) && patch -Np1 -i $(DIR_SRC)/src/patches/strongswan-5.3.1-build-timeattack.patch
cd $(DIR_APP) && patch -Np1 -i $(DIR_SRC)/src/patches/strongswan-ipfire.patch
- cd $(DIR_APP) && autoreconf -vfi
cd $(DIR_APP) && ./configure \
--prefix="/usr" \
--sysconfdir="/etc" \
diff --git a/src/patches/strongswan-5.3.1-build-timeattack.patch b/src/patches/strongswan-5.3.1-build-timeattack.patch
deleted file mode 100644
index 948c4fc..0000000
--- a/src/patches/strongswan-5.3.1-build-timeattack.patch
+++ /dev/null
@@ -1,11 +0,0 @@
---- strongswan-5.3.1/scripts/Makefile.am.old 2015-06-04 17:20:43.539244145 +0000
-+++ strongswan-5.3.1/scripts/Makefile.am 2015-06-04 17:20:51.760510631 +0000
-@@ -42,7 +42,7 @@
- dnssec_LDADD = $(top_builddir)/src/libstrongswan/libstrongswan.la
- aes_test_LDADD = $(top_builddir)/src/libstrongswan/libstrongswan.la
- settings_test_LDADD = $(top_builddir)/src/libstrongswan/libstrongswan.la
--timeattack_LDADD = $(top_builddir)/src/libstrongswan/libstrongswan.la
-+timeattack_LDADD = $(top_builddir)/src/libstrongswan/libstrongswan.la $(RTLIB)
-
- key2keyid.o : $(top_builddir)/config.status
-
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-06-12 15:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150612151706.A798F221D0@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/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