From owner-freebsd-security@FreeBSD.ORG Thu Jul 3 15:21:24 2014 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 733917F3 for ; Thu, 3 Jul 2014 15:21:24 +0000 (UTC) Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D66B2498 for ; Thu, 3 Jul 2014 15:21:24 +0000 (UTC) Received: by mail-qa0-f53.google.com with SMTP id j15so309479qaq.40 for ; Thu, 03 Jul 2014 08:21:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7AQkGioBSLPirfXIJ/Nol2WCdgmkxtM2mlC+xdVQQXQ=; b=uqmi3Gxh+Pw+LLgqqZVoyzNzc6K8Ska3db6WLf9FGLqbVY5bpek1lmzmg/ufSNEj8O j9C73nB8o0tkKhyOqgKuAK0YGE9u7ZiY7PNZiWz8UiLY54f3a/faVcfGm57dQOVKk48N znAMtaN9fRcSa7aRWd9Or66Q77NfGU1u6uIb4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=7AQkGioBSLPirfXIJ/Nol2WCdgmkxtM2mlC+xdVQQXQ=; b=GQxJs1kKGJA5t5Ot0Ac0/Gua5iZxXLC7W7mHSWsQ5eE8bmFcuA0aj+rI90bms31z3p 1vPvhvYLcOAsrdUfvIpzN2BRIofm0tMXbT1UYhuTXAvyJHDP3K2OXVVuKHb+MmUZAPu1 4uZx7gUG5Zn8+fejnUxCAk55upeZREJzpiSu8VoRxph9VJpelOwAk9RiNJqMLSqLPEka roycVshnIMBRSopFDXPWPFIjXUcQhkhhPt45O8a6ItFiiG+4s5qIERIUmVWOL6scHEnG KWAW58zcdNw3fYxmevNjEACeaQWN9guE2EaETykz3xVI30A1ZlZtO2fodUC8LiynN/Ff 8eNA== X-Gm-Message-State: ALoCoQmhHwx2C3cZq75xbbZy5R/wXTmEP1hlLHJq4m+cRcpSYb6JkJBH9pz54qOyLMcXe08hrrh2 X-Received: by 10.224.7.202 with SMTP id e10mr8477761qae.15.1404400883034; Thu, 03 Jul 2014 08:21:23 -0700 (PDT) MIME-Version: 1.0 Received: by 10.96.88.132 with HTTP; Thu, 3 Jul 2014 08:20:51 -0700 (PDT) In-Reply-To: <53B56F49.7030109@FreeBSD.org> References: <53B499B1.4090003@delphij.net> <53B4B7FB.6070407@FreeBSD.org> <53B56F49.7030109@FreeBSD.org> From: Eitan Adler Date: Thu, 3 Jul 2014 08:20:51 -0700 Message-ID: Subject: Re: RFC: Proposal: Install a /etc/ssl/cert.pem by default? To: Jonathan Anderson Content-Type: text/plain; charset=UTF-8 Cc: d@delphij.net, Ben Laurie , gecko@freebsd.org, Bryan Drewery , freebsd-security@freebsd.org, FreeBSD Ports Management Team , re , Jung-uk Kim X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2014 15:21:24 -0000 On 3 July 2014 07:57, Jonathan Anderson wrote: > Just my $.02, but if the FreeBSD project is to maintain a > ca-root-freebsd.pem, I think it should have one certificate in it: the root > FreeBSD Project cert. Beyond that, I'm not willing to vouch for the > trustworthiness of any CA, and I don't think the Project should either. Perhaps we should remove HTTPS support from libfetch and require the user to install wget or curl if they want to use SSL? Having a *default* certificate bundle (that could be removed / edited, of course) is not necessarily even making a trust claim about a particular cert. [0] IMHO the position where the majority of SSL on the internet is broken by default is not tenable. We support HTTP. We don't support HTTPS. The browsers spend a lot of time on this problem. We don't. I am not asserting that the Mozilla set is perfect. I am asserting that we should have *functional* SSL in the base system, and that using the Mozilla set is a good way to obtain that with a good enough policy. [0] It might be, but doesn't have to be [1] See https://wiki.mozilla.org/CA:How_to_apply and https://groups.google.com/forum/#!forum/mozilla.dev.security.policy -- Eitan Adler