An issue has been found where radsecproxy accepts TLS clients when it should not, due to the way it performs client verification after a TLS handshake.
See for more details: https://project.nordu.net/browse/RADSECPROXY-43 https://project.nordu.net/browse/RADSECPROXY-44 A (short term) fix for this issue has been released as version 1.6.1. Other changes in previously released version 1.6 mostly apply to F-Ticks logging, an optional feature that is not enabled in the OpenWRT package, due to a build dependency on nettle, a library that has not been ported/ packaged (yet). Signed-off-by: Zenon Mousmoulas <zmo...@noc.grnet.gr> --- package/feeds/packages/radsecproxy/Makefile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --exclude .svn --new-file -uprN a/package/feeds/packages/radsecproxy/Makefile b/package/feeds/packages/radsecproxy/Makefile --- a/package/feeds/packages/radsecproxy/Makefile 2012-10-16 18:37:12.000000000 +0300 +++ b/package/feeds/packages/radsecproxy/Makefile 2012-10-16 18:38:37.000000000 +0300 @@ -8,12 +8,12 @@ include $(TOPDIR)/rules.mk PKG_NAME:=radsecproxy -PKG_VERSION:=1.5 -PKG_RELEASE:=2 +PKG_VERSION:=1.6.1 +PKG_RELEASE:=1 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz PKG_SOURCE_URL:=http://software.uninett.no/radsecproxy/ -PKG_MD5SUM:=c65742a1b471c572ca7f6d11000d41f5 +PKG_MD5SUM:=841ec9b1492a7c7ae301a05ab035d85d PKG_INSTALL:=1 _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
