From owner-freebsd-security@freebsd.org Fri Sep 18 12:21:34 2015 Return-Path: Delivered-To: freebsd-security@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 2444D9CE800 for ; Fri, 18 Sep 2015 12:21:34 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (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 EE8C11834 for ; Fri, 18 Sep 2015 12:21:33 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E3340209CD for ; Fri, 18 Sep 2015 08:21:32 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Fri, 18 Sep 2015 08:21:32 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=no8RDh/MLCBHfuf WJRkCxD2kFlE=; b=PmttRXE27dSz0zuKqx7Fu8oet7NDNudHW6kNKfp3kmb99GL BCBOldMq3ZEFOo8Y/bLbXUR8vQ1uAytfPuwinrVxrLKdZBRuRbC+RPDsM5mS9mKv YttFM36Ch05rZIZ+DH0InJvZ7desX/2a8VB52svGvX2uiT/ZnvRW6VNCa1mc= Received: by web3.nyi.internal (Postfix, from userid 99) id BE09410CD69; Fri, 18 Sep 2015 08:21:32 -0400 (EDT) Message-Id: <1442578892.1807598.387215049.07156D0F@webmail.messagingengine.com> X-Sasl-Enc: Yqbv6rL/6rf1N7JxT+j0B4NoAd3RXIlDbU6tV5sE9lMv 1442578892 From: Mark Felder To: grarpamp , freebsd-security@freebsd.org Cc: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-e92f8263 Subject: Re: HTTPS on freebsd.org, git, reproducible builds Date: Fri, 18 Sep 2015 07:21:32 -0500 In-Reply-To: References: X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2015 12:21:34 -0000 On Thu, Sep 17, 2015, at 22:20, grarpamp wrote: > Is there some reason "freebsd.org" and all it's > subdomains don't immediately 302 over to > https foreverafter? > What good does https on freebsd.org provide except checking a box that some people are obsessed about right now? You're adding another layer of complexity. The front page, documentation, handbooks, etc are not sensitive data. There are two different opinions on this matter throughout the project: * Encrypt all the things * Encrypt what is necessary If FreeBSD is visibly penalized by Google in the future for not hosting on https it might be worth doing. > Same goes for use of svn, which has no native > signable hashed commit graph, as freebsd's > canonical repo... instead of git which does. > svn is available over https > Not to mention the irreproducible builds / pkgs / ISO's. > Nobody is doing this successfully yet. Last I checked Debian is closest. But keep in mind this is not a security feature, it's debugging feature. You still need to solve backdoored compilers ("use this new double compiler method!" OK...) and then you need to solve backdoored hardware. > These days these flaws are more than a bit ridiculous, > especially for an OS, which by definition [excepting > the hardware] should be your root of trust. > > Can we get a wiki project page and some traction on this? > Thanks. > https://wiki.freebsd.org/ReproducibleBuilds -- Mark Felder ports-secteam member feld@FreeBSD.org