From owner-freebsd-questions@FreeBSD.ORG Tue May 20 07:32:55 2014 Return-Path: Delivered-To: freebsd-questions@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 DC4DF2A6 for ; Tue, 20 May 2014 07:32:55 +0000 (UTC) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (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 5FF4826EA for ; Tue, 20 May 2014 07:32:55 +0000 (UTC) Received: by mail-la0-f44.google.com with SMTP id hr17so57607lab.3 for ; Tue, 20 May 2014 00:32:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=HcSMfNAZbbvVvICjSQs5VIHvjkWpkR8ijyeQqXkFNC4=; b=hXeegUoLBQ9JxBfa76ixbFs/4kFkrH2XYbKlOO8+4JX3BhHqO6u5wevWpL8Ax/333N Xqa9D1l7JezFZ/ugoG9om6tlQBJe8f2QTo7M7Eh6ewqZcKO0iOx2BMaOjlLrVWV/Ab/1 oODK9nuNy6y7Sg+66HbhFlZ1V3Xi2CFjYd0859NpiEwPedb37lpE02wJXVtk3bqvAwpF M9Ejk4tEnlZXRZqNT2oKXdb705uwzeOBabP5gXsZNcXTmvUnlSbcTd9wZOxziETI8QYm AWc462zW8TaMsZ2moaHszEf+lRCBSjl3oNOLfKRdKz4H3lGeZwF61fQFcZTpeojdxD0v TpwA== X-Received: by 10.152.115.232 with SMTP id jr8mr9575641lab.6.1400571173284; Tue, 20 May 2014 00:32:53 -0700 (PDT) Received: from blazon-pc.rw.local ([78.84.244.14]) by mx.google.com with ESMTPSA id i10sm19998145lbc.16.2014.05.20.00.32.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 20 May 2014 00:32:52 -0700 (PDT) Message-ID: <537B0522.8090109@gmail.com> Date: Tue, 20 May 2014 10:32:50 +0300 From: Alnis Morics User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: MITM attacks against portsnap and freebsd-update References: <537A704D.6010209@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 07:32:55 -0000 On 05/20/2014 09:51, n j wrote: > On Tue, May 20, 2014 at 12:03 AM, David Noel wrote: > >> On 5/19/14, Alnis Morics wrote: >>> On 05/19/2014 23:28, David Noel wrote: >>>> I also think it would be an appropriate time to discuss retiring >>>> portsnap. >>> Subversion checkouts and updates take much more time than Porstnap. >> My experience has been that both portsnap and svn update typically >> take under a minute to complete. >> >> Regardless, don't most people run this in the background with portsnap >> cron? >> > I don't. And I don't regularly update the ports tree. > > When you regularly update ports tree, the diffs svn update needs to pull > are relatively small. When you update, say, once a month, portsnap in my > experience gets the job done a lot quicker. > > My $.02, Exactly. And "svn checkout" is incomparably slower than "portsnap fetch extract". -Alnis