Date: Thu, 13 Apr 2017 07:40:48 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212149] security/strongswan: Build with libressl 2.4 causes runtime failure: Undefined symbol "CMS_RecipientInfo_ktri_get0_signer_id" Message-ID: <bug-212149-13-l0dZ7DoAQS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-212149-13@https.bugs.freebsd.org/bugzilla/> References: <bug-212149-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212149 --- Comment #10 from Franco Fichtner <franco@opnsense.org> --- (In reply to dewayne from comment #9) Looks like it. Still the best option. I tried to ask LibreSSL if we could have an optional workaround for targeted builds as pinning the OpenSSL version in general is tricky. For 2.4.x it w= orks well, but 2.5.x was just released so I don't know where that will lead. http://marc.info/?l=3Dlibressl&m=3D147816235401460&w=3D2 No more responses or incentives there as well. Eventually, strongSwan need= s to be made aware of how feature macros or libressl version numbers are used to achieve the same. I think that's something we need to do and push upstream ourselves. Cheers, Franco --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212149-13-l0dZ7DoAQS>