From owner-freebsd-ports-bugs@freebsd.org  Thu Apr 13 07:40:50 2017
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
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 BE958D3B270
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Thu, 13 Apr 2017 07:40:50 +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 ACB6F1CB
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 13 Apr 2017 07:40:50 +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 v3D7emoE018709
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 13 Apr 2017 07:40:50 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
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"
Date: Thu, 13 Apr 2017 07:40:48 +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-patch, needs-qa
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: franco@opnsense.org
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: 
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/>
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 <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 07:40:50 -0000

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.=