From owner-freebsd-ports@freebsd.org Fri Jul 8 19:20:37 2016 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 CD4B7B839C1 for ; Fri, 8 Jul 2016 19:20:37 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from msa1.earth.yoonka.com (yoonka.com [185.24.122.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "msa1.earth.yoonka.com", Issuer "msa1.earth.yoonka.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B05E1B6F for ; Fri, 8 Jul 2016 19:20:36 +0000 (UTC) (envelope-from list1@gjunka.com) Received: from crayon2.yoonka.com (crayon2.yoonka.com [10.70.7.20]) (authenticated bits=0) by msa1.earth.yoonka.com (8.15.2/8.15.2) with ESMTPSA id u68JKSvZ096505 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 8 Jul 2016 19:20:28 GMT (envelope-from list1@gjunka.com) Subject: Re: base components should always be default (Re: change in default openssl coming) To: freebsd-ports@freebsd.org References: From: Grzegorz Junka Message-ID: Date: Fri, 8 Jul 2016 19:20:28 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jul 2016 19:20:37 -0000 On 08/07/2016 16:29, Mikhail T. wrote: > On 08.07.2016 02:26, Mathieu Arnold wrote: >> During this summer (sometime in August I think) I will be changing the default OpenSSL for the ports tree from the base system version to security/openssl. > The short answer is "Why?!" The longer reaction is: "please don't". > > Certainly not without a lengthy and exhaustive discussion (or flame-war, > if you will), which shall arrive at a consensus -- and, if it does not, > then no change shall happen. > > Generally, we should be eating our own dog-food -- using base-provided > components for everything by default where at all possible. If the base > OpenSSL is in some way(s) deficient, well, that's an argument for > updating the base. The base comes with not just the libraries, but withe > accompanying header-files -- meaning, the developers are free to use > those libraries. So the ports certainly should be doing just that. > > Our ports and the packages derived from them are part of FreeBSD -- and > the various components need to remain tightly integrated. > > Yes, I understand, you intend for there to remain an option, which the > holdouts like myself will be able to use to retain the old behavior. But > that's not good enough -- if the default packages will be built > differently, then bitrot will creep in and building against the base > will slowly become more and more difficult. > >> I will also, because it goes with it, change the default GSSAPI from base to something else, > Sorry, what goes with what? Are you saying, Heimdal can't be built with > port's OpenSSL or vice versa? > > -mi > > The only reason I heard why base isn't updated with the proper package from ports is because of security implications. Older versions are more security-tested and therefore safer. If there is a vulnerability in the base it's much more hassle to update the base than ports. I don't have my opinion and sometimes it's annoying to not be able to use the base version, but putting everything into base is certainly an option if only the process of updating the base was light and quick enough. Is it like that now? Maybe with the incoming release cycle from FreeBSD-11? Grzegorz