Date: Sat, 12 Apr 2014 14:33:44 +0200 From: dt71@gmx.com To: freebsd-hackers@freebsd.org Subject: Re: MITM attacks against portsnap and freebsd-update Message-ID: <534932A8.6040801@gmx.com> In-Reply-To: <CAHAXwYCGkP-o0VvMXj5S8-KNA45aTvy%2BsrjDL_=8-x9Dza5z5Q@mail.gmail.com> References: <CAHAXwYCGkP-o0VvMXj5S8-KNA45aTvy%2BsrjDL_=8-x9Dza5z5Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Noel wrote, On 04/10/2014 19:03: > The reason I see for it to be retired is that subversion allows us to > easily and securely check out the ports tree. It's a one-line command: > `svn co https://...`. Keeping it up-to-date it is another one-liner: > `cd /usr/ports; svn update`. With the inclusion of svnlite in base, > the portsnap code and servers acting as mirrors become redundant and > seem like a waste of resources. One-liners are also sufficient for Portsnap. Subversion, due to its scheme of keeping an uncompressed copy of each file in .svn trees, wastes ~410MiB of disk space (for ports; additionally, ~820MiB for src) for users who only want to build ports from source, not develop; whereas Portsnap wastes only ~140MiB. Subversion is more of a resource strain on both clients and servers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?534932A8.6040801>