Date: Fri, 18 Sep 2015 10:06:07 -0400 From: Nathan Dorfman <na@rtfm.net> To: Daniel Feenberg <feenberg@nber.org> Cc: grarpamp <grarpamp@gmail.com>, freebsd-security@freebsd.org, freebsd-questions@freebsd.org Subject: Re: HTTPS on freebsd.org, git, reproducible builds Message-ID: <20150918140555.GA14677@vane> In-Reply-To: <alpine.LRH.2.11.1509180646470.14490@nber4.nber.org> References: <CAD2Ti2_YNkNi2b=PzFCwu3PVaP8hOzADys3=-k0AqvsDRhJpzA@mail.gmail.com> <alpine.LRH.2.11.1509180646470.14490@nber4.nber.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 18, 2015 at 07:45:29AM -0400, Daniel Feenberg wrote: > 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. There may be no reason to encrypt it, but there's plenty of reason to authenticate it. That is, when you browse FreeBSD.org, you'd probably prefer to know that the content wasn't modified in transit to include a 0-day JavaScript exploit. -nd.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150918140555.GA14677>