From owner-freebsd-ports-bugs@freebsd.org Tue Apr 25 02:22:40 2017 Return-Path: Delivered-To: freebsd-ports-bugs@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 AC678D4E802 for ; Tue, 25 Apr 2017 02:22:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 810991897 for ; Tue, 25 Apr 2017 02:22:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3P2MalC082797 for ; Tue, 25 Apr 2017 02:22:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212149] security/strongswan: Runtime failures with LibreSSL Date: Tue, 25 Apr 2017 02:22:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: dewayne@heuristicsystems.com.au X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? merge-quarterly? X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Apr 2017 02:22:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212149 dewayne@heuristicsystems.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #182037|0 |1 is obsolete| | --- Comment #17 from dewayne@heuristicsystems.com.au --- Created attachment 182070 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D182070&action= =3Dedit libressl Makefile patch - helps migration to libressl Bernard, Thanks for your help. After a few more iterations, of chasing my tail with patches, I decided that this game had to end. I hacked /usr/include/openssl/opensslv.h #define OPENSSL_VERSION_NUMBER 0x1000107fL /* openssl at time of libressl f= ork */ /* #define OPENSSL_VERSION_NUMBER 0x20000000L Just to test if strong= swan will ever work!*/ and for good measure "ln -s /usr/local/include/openssl /usr/include/openssl= ". I moved my working copies of strongswan and hostapd; svnlite pulled the latest and rebuilt. I've added my patch to the libressl Makefile, which I've included (discard = my CFLAGS change as that is local. I only use/tested on amd64, hence the constraint. Result strongswan 5.5.2, and other problematic ports: freeradius3, haproxy and hos= tapd 2.6 all built cleanly and preliminary testing looks positive. Perhaps not a long-term solution, and I'm sure we need to get this fixed for the long haul. My realistic expectation - ALL upstream applications that use openssl 1.0.X internals in their source, are going to need to change/'hack around' to accomodate the new openssl 1.1.x (opaque) structures. At which point we'll need to address properly, but until openssl 1.0.x retires &/or libressl changes significantly we "should" be ok until then.=20=20 For me, the key trigger for change will be, who actually provides safe ECC,= but that's another story. ;) --=20 You are receiving this mail because: You are the assignee for the bug.=