From owner-freebsd-current@freebsd.org Wed Dec 13 02:05:11 2017 Return-Path: Delivered-To: freebsd-current@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 05F5BE8D558 for ; Wed, 13 Dec 2017 02:05:11 +0000 (UTC) (envelope-from bsd-lists@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 970A47D90A for ; Wed, 13 Dec 2017 02:05:10 +0000 (UTC) (envelope-from bsd-lists@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 vBD26WY3009452; Tue, 12 Dec 2017 18:06:38 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "FreeBSD Current" In-Reply-To: <20171213015826.36qor4ecm3kprnu4@mutt-hbsd> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Shawn Webb" Subject: Re: Replacing OpenSSL in base -- does it work? Date: Tue, 12 Dec 2017 18:06:38 -0800 Message-Id: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Dec 2017 02:05:11 -0000 On Tue, 12 Dec 2017 20:58:26 -0500 "Shawn Webb" said > On Tue, Dec 12, 2017 at 05:57:29PM -0800, Chris H wrote: > > Hi all, > > I just fired off a fresh build on a new 12-CURRENT install=2E But forgot > > to add WITHOUT_OPENSSL to src=2Econf(5), as I had intended to=2E :-( > > Anyway, I'd like to remove OpenSSL from base=2E Any recommendations on th= e > > best approach, and best alternatives? >=20 > Both HardenedBSD and TrueOS use LibreSSL in base=2E WOW=2E Thanks for the fast reply, Shawn! I had already considered that might be a good direction=2E Nice to hear it works! Thanks again, Shawn! --Chris >=20 > Thanks, >=20 > --=20 > Shawn Webb > Cofounder and Security Engineer > HardenedBSD >=20 > GPG Key ID: 0x6A84658F52456EEE > GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE