From owner-freebsd-hackers@FreeBSD.ORG Fri Apr 11 21:20:39 2014 Return-Path: Delivered-To: freebsd-hackers@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 82C1EC6 for ; Fri, 11 Apr 2014 21:20:39 +0000 (UTC) Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) (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 435EB1DEA for ; Fri, 11 Apr 2014 21:20:39 +0000 (UTC) Received: by mail-qa0-f47.google.com with SMTP id m5so3836626qaj.20 for ; Fri, 11 Apr 2014 14:20:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Zai8ULvZN+cWCqGZpsnioUi27p67tjGEvQi+SgIyaGo=; b=e+yVWVBMXz+SsSlWdR7ZVBd47+Poqi+idNVj0teg3dEEHe1K91PO5XxmytoW7dsTgq fAm2h2qU1T61qq9lJGRnFgsV2Cgs2c/5yhGOPUHUh4fPD63dlT2YP7mfFkg3CSVJsYIE EZd7u9FqHOZdZzBW7G2w1X9svf9iz7zetG+jb8RLiv3sqoo+S9Ou/+k7XVQ6IQx1CkyK kHiAnL9kthqsuCnz5EqENeL1KTBX/83kyI+KliHTHrOggj8jNovsuPbKqDyYwZyASrXd QjH6yfzhtfRO7tH9WFcBOy1rf90o+POWaSBGxe9HXVsAyzKvTvkR/FU+Z0g91ui97Q72 /J1A== X-Received: by 10.140.51.14 with SMTP id t14mr30761835qga.50.1397251238321; Fri, 11 Apr 2014 14:20:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.72.131 with HTTP; Fri, 11 Apr 2014 14:20:18 -0700 (PDT) In-Reply-To: <2012148.SzKMgBGQYg@desktop.reztek> References: <2012148.SzKMgBGQYg@desktop.reztek> From: Anton Afanasyev Date: Fri, 11 Apr 2014 14:20:18 -0700 Message-ID: Subject: Re: MITM attacks against portsnap and freebsd-update To: Matthew Rezny X-Mailman-Approved-At: Fri, 11 Apr 2014 21:38:33 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 21:20:39 -0000 On Fri, Apr 11, 2014 at 11:04 AM, Matthew Rezny wrote: > The biggest effort would be adding rsync to base, but being that we have > svn(lite) in base it should not be a big deal to add rsync. > I may be too naive and/or just not understand things as well as those who do move code into base, so excuse my ignorance, but why was svnlite moved into base, and why even consider moving rsync into base? Sure, it is nice if the base includes everything needed to allow development of it; it is also a must to be able to update and build your ports. But why include tools that do this, rather than a bootstrap for installing those tools? For developing and updating base, why not include a script that fetches a (sufficiently fresh) snapshot of the ports tree and let the user decide whether they want to use svn or any other port to update their sources? If it is deemed too large a download (a valid concern) - download only svn and its dependencies, possibly even to a ports tree rooted in a location different from /usr/ports, and build svn from that. For keeping ports up to date, why not include a script that fetches a (sufficiently fresh) copy of the ports tree and tell the user that the preferred method to update is rsync; heck, create a port that uses rsync to do what Matthew described above, and /offer/ to install it for the the user from the tree that was just downloaded. Something along the lines of the above would completely remove the need to keep unrelated code in base - and the need to keep it updated - , while still allowing the end user to keep base and ports up to date. Anton