From owner-freebsd-ports@FreeBSD.ORG Thu May 15 11:22:36 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 77105EF5 for ; Thu, 15 May 2014 11:22:36 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2CF212CE2 for ; Thu, 15 May 2014 11:22:36 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WktkB-0007oX-4R; Thu, 15 May 2014 13:22:35 +0200 Date: Thu, 15 May 2014 13:22:35 +0200 From: Kurt Jaeger To: Dewayne Geraghty Subject: Re: Committer to address 2 CVE's against strongswan Message-ID: <20140515112235.GX2341@home.opsec.eu> References: <5373EE24.4030007@heuristicsystems.com.au> <20140515084921.GV2341@home.opsec.eu> <53749892.4050309@heuristicsystems.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53749892.4050309@heuristicsystems.com.au> Cc: strongswan@nanoteq.com, freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2014 11:22:36 -0000 Hi! > Thank-you for taking the time to look into this. The configuration used > in the final build isn't standard, and comprises: > CURL=on: Enable CURL to fetch CRL/OCSP > EAPRADIUS=on: Enable EAP Radius proxy authentication > IKEv1=on: Enable IKEv1 support > XAUTH=on: Enable XAuth password verification strongswan has many options and covering all those is not easy (and not part of my build-testing it 8-) The issue would be feature-testing it, but I hope I'm into gardening as a new career when this happens 8-) > The environment is 9.2Stable i386 and amd64 as of 5th May. Built > without both pkg_ng and poudriere. > > The entire tree was rebuilt on May 10 (all ports deleted, rebuilt and > reinstalled on two build and four test machines). Strongswan and > libexecinfo have been rebuilt a few times since then as I've added > --enable-padlock to the build. I'm not sure I'm following you here. The patch from the maintainer in PR 189132 does probably not contain your --enable-padlock change, right ? Would you mind to submit a seperate PR with the change ? > So its disappointing that > you've come across these errors, but does raise the prospect that > migrating to next gen tools might enhance quality control - a benefit. Yes, and the pkg-plist issue was easy to fix 8-) -- pi@opsec.eu +49 171 3101372 6 years to go !