From owner-freebsd-security@FreeBSD.ORG  Fri Jul  4 12:30:33 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4788F14A;
 Fri,  4 Jul 2014 12:30:33 +0000 (UTC)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 (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 21CE82530;
 Fri,  4 Jul 2014 12:30:33 +0000 (UTC)
Received: from janderson.engr.mun.ca (localhost [127.0.0.1])
 by freefall.freebsd.org (8.14.8/8.14.8) with ESMTP id s64CUUl3095493;
 Fri, 4 Jul 2014 12:30:32 GMT (envelope-from jonathan@FreeBSD.org)
Message-ID: <53B69E65.7020507@FreeBSD.org>
Date: Fri, 04 Jul 2014 10:00:29 -0230
From: Jonathan Anderson <jonathan@FreeBSD.org>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Dan Lukes <dan@obluda.cz>, d@delphij.net, freebsd-security@freebsd.org,
 gecko@freebsd.org
Subject: Re: RFC: Proposal: Install a /etc/ssl/cert.pem by default?
References: <53B499B1.4090003@delphij.net> <53B4A337.3010907@obluda.cz>
 <CAF6rxgkhXtXCjWGpbcm0UU3Rr57dXJojQJ05Rqe-sQ_Nmyp8KQ@mail.gmail.com>
 <53B4BFD2.2060903@obluda.cz> <53B499B1.4090003@delphij.net>
 <53B4A337.3010907@obluda.cz> <20140704024451.GU45513@funkthat.com>
In-Reply-To: <20140704024451.GU45513@funkthat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Jul 2014 12:30:33 -0000

John-Mark Gurney wrote:
> Dan Lukes wrote this message on Thu, Jul 03, 2014 at 02:26 +0200:
>> If I consider a CA to be trustworthy, I will insert it's certificate to
>> trusted store. No one is welcomed to make such decision in behalf of me.
>
> As others have said, you can customize FreeBSD how you want.. There
> is no, we will uninstall FreeBSD if you uninstall (or set WITHOUT_xxx)
> on your FreeBSD system...


So we agree that customization is required, the question is what a user 
has to do to effect this customization:

1. install a package (possibly included on the install media), or
2. set WITHOUT_MOZILLA_CA_BUNDLE and rebuild FreeBSD.

To me, the approach that doesn't require "rebuild FreeBSD" is the 
simpler one.

It also doesn't require a Security Advisory every time a CA gets dropped 
from Mozilla's bundle (which ought to happen a lot). Ports get updated, 
people get that. I don't think we should introduce things in the base 
system that we *know* will require SAs, freebsd-update, etc.


Jon
-- 
Jonathan Anderson
jonathan@FreeBSD.org