From owner-freebsd-ports@freebsd.org Mon Aug 21 17:47:00 2017 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 879F8DEAB43 for ; Mon, 21 Aug 2017 17:47:00 +0000 (UTC) (envelope-from david@dafnet.se) Received: from datawebb.dafcorp.net (unknown [IPv6:2001:470:6c08:13::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 588667D955 for ; Mon, 21 Aug 2017 17:46:59 +0000 (UTC) (envelope-from david@dafnet.se) Received: from [172.16.98.137] (unknown [195.198.171.84]) by datawebb.dafcorp.net (Postfix) with ESMTPSA id E929BEAE for ; Mon, 21 Aug 2017 19:46:57 +0200 (CEST) Subject: Re: security/libressl: Add the possibility to build only libtls To: freebsd-ports@freebsd.org References: <0f189ca5-76d8-f05c-b03c-31ff5e8a3113@dafnet.se> From: David Wahlund Message-ID: <2a820c5e-b6cf-9496-4e37-ee8a8dbe7beb@dafnet.se> Date: Mon, 21 Aug 2017 19:46:55 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <0f189ca5-76d8-f05c-b03c-31ff5e8a3113@dafnet.se> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Aug 2017 17:47:00 -0000 On 2017-08-21 11:59, David Wahlund wrote: > Hi > I'd like to use the libtls library of LibreSSL on FreeBSD. Or the python > bindings to libtls specifically. I do NOT however want to replace > openssl or use the libssl library. > > From what I understand it would be possible in practice as I assume it's > only libssl that overwrites files used by openssl. > > Would it be possible to create an option in LibreSSL, or preferably make > a separate port, for libtls only? That way future ports can depend on > libtls only. For example a future python-libtls port could depend on that. > > -David I guess it's the libtls-standalone I'm after. It's on GitHub. https://github.com/libressl-portable/portable/tree/master/libtls-standalone