From owner-freebsd-ports@freebsd.org Thu Aug 25 14:42:06 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF3D8BC5BDE for ; Thu, 25 Aug 2016 14:42:06 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.kissl.de (host64.kissl.de [213.239.241.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.shmhost.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 97E141579; Thu, 25 Aug 2016 14:42:06 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (ipservice-092-208-160-166.092.208.pools.vodafone-ip.de [92.208.160.166]) (Authenticated sender: web104p1) by host64.kissl.de (Postfix) with ESMTPSA id 76F486B7DB; Thu, 25 Aug 2016 16:34:50 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: libressl and strongswan From: Franco Fichtner In-Reply-To: <20160825172316.2e04f55c3a6066d3661c0eab@abinet.ru> Date: Thu, 25 Aug 2016 16:34:49 +0200 Cc: freebsd-ports , Bernard Spil Content-Transfer-Encoding: quoted-printable Message-Id: <198ED4B0-0BCF-4453-B7E4-0C8541FD955E@lastsummer.de> References: <20160825172316.2e04f55c3a6066d3661c0eab@abinet.ru> To: abi X-Mailer: Apple Mail (2.3124) X-Virus-Scanned: clamav-milter 0.99.2 at host64.kissl.de X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Aug 2016 14:42:06 -0000 Hi, > On 25 Aug 2016, at 4:23 PM, abi wrote: >=20 > I tried different DH groups without any success, so I suppose = strongswan is broken. I can confirm this, the only workarounds I have seen so far are = reverting to LibreSSL 2.3.7 or compiling it against base if your LibreSSL is locked = in. Maybe this is simply an issue of incomplete adaption of strongSwan to LIBRESSL_VERSION_NUMBER? Cheers, Franco=