aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndreas Steffen <andreas.steffen@strongswan.org>2011-11-08 21:00:09 +0100
committerAndreas Steffen <andreas.steffen@strongswan.org>2011-11-08 21:00:09 +0100
commitacb92cb44c925835e7aff6788f9f4ea196db0644 (patch)
treeabd91de247903c812bb7cde9b53569762fb9a1f6
parente7cb8f9b37b4b0d181282064777edbb11953cd0e (diff)
downloadstrongswan-acb92cb44c925835e7aff6788f9f4ea196db0644.tar.bz2
strongswan-acb92cb44c925835e7aff6788f9f4ea196db0644.tar.xz
version bump to 4.6.1
-rw-r--r--NEWS17
-rw-r--r--configure.in2
2 files changed, 18 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index 313242be3..0a9b566b0 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,20 @@
+strongswan-4.6.1
+----------------
+
+- Because of changing checksums before and after installation which caused
+ the integrity tests to fail we avoided directly linking libsimaka, libtls and
+ libtnccs to those libcharon plugins which make use of these dynamic libraries.
+ Instead we linked the libraries to the charon daemon. Unfortunately the most
+ recent libtool versions do no keep links to dynamic libraries that are not
+ actually used by the charon daemon itself, thus causing failures during the
+ loading of the plugins which depend on these libraries for resolving external
+ symbols.
+
+- Therefore our approach of computing integrity checksums for plugins had to be
+ changed radically by moving the hash generation from the compilation to the
+ post-installation phase.
+
+
strongswan-4.6.0
----------------
diff --git a/configure.in b/configure.in
index a0b1f40fd..66daeb6b8 100644
--- a/configure.in
+++ b/configure.in
@@ -16,7 +16,7 @@ dnl ===========================
dnl initialize & set some vars
dnl ===========================
-AC_INIT(strongSwan,4.6.0)
+AC_INIT(strongSwan,4.6.1)
AM_INIT_AUTOMAKE(tar-ustar)
AC_CONFIG_MACRO_DIR([m4/config])
PKG_PROG_PKG_CONFIG