From owner-freebsd-security@freebsd.org Fri Sep 18 14:07:38 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 119FC9CEEE6 for ; Fri, 18 Sep 2015 14:07:38 +0000 (UTC) (envelope-from ben.bailess@gmail.com) Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com [IPv6:2607:f8b0:4002:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C50711B61 for ; Fri, 18 Sep 2015 14:07:37 +0000 (UTC) (envelope-from ben.bailess@gmail.com) Received: by ykdg206 with SMTP id g206so47366928ykd.1 for ; Fri, 18 Sep 2015 07:07:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=QgXPWmbtE/tZF9Bw6NOwCuZUhLyMINrrSBrp24C93Cw=; b=u7kAiahzz/PoZJ9uxPDXlKuYjXt2vvyRwaLK8VkV8hiGYX6Pios2wtIddpsUJsAyWu AYwMu43qvLiuJ5FXsbTHaSCSYYDQq6DhYAHjwCpTCe9MV9JhD+v+1FA+jn3beZPJFQys wsYlUoixJL1icwP8RaMymo/jv8O0pj9v6JRbRS0T+L1pLV2gyCssn6kkk5nOvu2ESYld SWJM5niZ1vPuEcnJApyo8o6X8ZXJdsKFESs7i1FjxSRwbqKFPpL4inLFJ8kNbi8dA5CI WI15xTl1J327T9OU6F1w8/Qcge7ejX24o54sre4X/XxCQAGVASRpvkI4wEl/nZh10U7C t4ng== MIME-Version: 1.0 X-Received: by 10.129.19.214 with SMTP id 205mr4682025ywt.130.1442585256923; Fri, 18 Sep 2015 07:07:36 -0700 (PDT) Received: by 10.37.119.73 with HTTP; Fri, 18 Sep 2015 07:07:36 -0700 (PDT) In-Reply-To: <7BAECC2B-5001-47D6-9199-8549697E7807@spam.lifeforms.nl> References: <7BAECC2B-5001-47D6-9199-8549697E7807@spam.lifeforms.nl> Date: Fri, 18 Sep 2015 10:07:36 -0400 Message-ID: Subject: Re: HTTPS on freebsd.org, git, reproducible builds From: Ben Bailess To: freebsd-security@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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 14:07:38 -0000 I have to echo this sentiment -- authentication is important, and so is integrity. HTTPS would provide both -- to be sure you're talking to the "real" FreeBSD and give you confidence that your page content has not been altered in transit by a network adversary (e.g. if you are using Tor)*. *I honestly don't see that being a realistic defense against NSA/GCHQ-level attackers, though... the coercive power they have over CAs would probably be the weak point there, in my opinion. HTTPS isn't a magic bullet by any means (which should be obvious), but it's also not worthless and would protect against at least some less-than-TLA-level network adversaries. On Fri, Sep 18, 2015 at 9:30 AM, Walter Hop wrote: > > > >> Is there some reason "freebsd.org" and all it's > >> subdomains don't immediately 302 over to > >> https foreverafter? > > > > Is there a reason to encrypt something that is completely public? > Perhaps to allow the visitor to conceal the fact that they are interested > in FreeBSD? That won't work, since the IP address of the server can't be > encrypted. I feel like I am missing something. > > Privacy is often important, but authentication (i.e. not having content > tampered with) may be more important in many cases. > > The US and UK governments are owning sysadmins who browse non-HTTPS sites= : > > http://www.spiegel.de/international/world/ghcq-targets-engineers-with-fak= e-linkedin-pages-a-932821.html > < > http://www.spiegel.de/international/world/ghcq-targets-engineers-with-fak= e-linkedin-pages-a-932821.html > > > > https://theintercept.com/2014/03/20/inside-nsa-secret-efforts-hunt-hack-s= ystem-administrators/ > < > https://theintercept.com/2014/03/20/inside-nsa-secret-efforts-hunt-hack-s= ystem-administrators/ > > > > The Chinese government hijacked non-HTTPS sessions to inject DDoS > javascript: > > https://www.eff.org/deeplinks/2015/04/china-uses-unencrypted-websites-to-= hijack-browsers-in-github-attack > < > https://www.eff.org/deeplinks/2015/04/china-uses-unencrypted-websites-to-= hijack-browsers-in-github-attack > > > > If often-used sites migrate to HTTPS (together with HSTS) these attacks > will become a lot harder. > > I=E2=80=99m also seeing more demand for HTTPS from customers. In Europe t= here has > been a lot of mainstream coverage of tech privacy issues, and various > non-technical people now distrust sites that don=E2=80=99t have =E2=80=9C= a lock=E2=80=9D. So it > also has credibility/PR benefits to use it by default. > > There is always effort involved in making the switch, but for most sites > and applications this is probably not an unreasonable amount given the > benefits. > > -- > Walter Hop | PGP key: https://lifeforms.nl/pgp > > _______________________________________________ > freebsd-security@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.or= g > " >