From owner-freebsd-ports@freebsd.org Fri Jan 5 04:46:21 2018 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 19B97EB0AEB for ; Fri, 5 Jan 2018 04:46:21 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C90AD74D89 for ; Fri, 5 Jan 2018 04:46:19 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w054kS9l002562; Thu, 4 Jan 2018 20:46:34 -0800 (PST) (envelope-from portmaster@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: , "Eugene Grosbein" , In-Reply-To: <5ea5e276-08da-aec9-ba81-b50ea96bf8c4@luckie.org.nz> From: "Chris H" Reply-To: portmaster@BSDforge.com To: "Matthew Luckie" Subject: Re: using security/openssl in a port Date: Thu, 04 Jan 2018 20:46:34 -0800 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Jan 2018 04:46:21 -0000 On Fri, 5 Jan 2018 17:16:30 +1300 "Matthew Luckie" said > On 1/5/18 5:09 PM, Eugene Grosbein wrote: > > On 05=2E01=2E2018 09:44, Matthew Luckie wrote: > >=20 > >> My main worry is that I could not find a single port that apparently > >> depends on security/openssl=2E I'm worried that its more complicated th= an > >> simply declaring a dependency on security/openssl on particular freebs= d > >> versions because other ports that use openssl might link against it > >> without registering a dependency=2E Is my worry misplaced? > >=20 > > Why don't you read the Porter's Handbook? It has answers to all your > > questions: > >=20 > > > > https://www=2Efreebsd=2Eorg/doc/en_US=2EISO8859-1/books/porters-handbook/uses= -ssl=2Ehtml >=20 > I already said that I considered USES =3D ssl and that it didn't seem to > address my concerns=2E Can you please point me at a port that depends on > OpenSSL from ports using USES =3D ssl (or whatever this page of the > porters handbook is trying to tell me to do)=2E >=20 > Thanks, >=20 > Matthew May I humbly suggest that you have a look at ports that near guarantee an *SSL option? Consider most of the web servers, and scripting languages, such as; php, python, and Perl=2E In fact I would venture a guess that most of the ports in the www category will hint to SSL=2E As well as the lang category, where the language is prominently used on the (inter)net=2E HTH --Chris