From owner-freebsd-security@FreeBSD.ORG Mon Apr 4 19:35:46 2011 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80AAC1065672 for ; Mon, 4 Apr 2011 19:35:46 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (75-101-96-57.dsl.static.sonic.net [75.101.96.57]) by mx1.freebsd.org (Postfix) with SMTP id 4B41D8FC0A for ; Mon, 4 Apr 2011 19:35:46 +0000 (UTC) Received: (qmail 35858 invoked by uid 1001); 4 Apr 2011 19:36:09 -0000 Date: Mon, 4 Apr 2011 12:36:09 -0659 From: "David E. Thiel" To: freebsd-security@freebsd.org Message-ID: <20110404193545.GN18694@redundancy.redundancy.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Face: %H~{$1~NOw1y#%mM6{|4:/ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2011 19:35:46 -0000 On Fri, Apr 01, 2011 at 03:32:51PM +0100, István wrote: > FreeBSD ships OpenSSL but it is broken because there is no CA. Right, > it is like shipping a car without wheels, I suppose. While I agree somewhat with your sentiment, SSL is not necessarily broken without CA certificates, as it's completely possible to do TOFU verification ala SSH. However, I think it's an appropriate time to mention again that there is at least one place in base that does indeed have broken SSL support, namely libfetch. To do SSL properly, you can do CA certificate verification or you can do TOFU, but libfetch still accepts any certificate it encounters, without user warning.