From owner-freebsd-questions@FreeBSD.ORG Sun Jun 15 13:38:21 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 D61D789D for ; Sun, 15 Jun 2014 13:38:21 +0000 (UTC) Received: from mail-vc0-x229.google.com (mail-vc0-x229.google.com [IPv6:2607:f8b0:400c:c03::229]) (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 948BE2B4A for ; Sun, 15 Jun 2014 13:38:21 +0000 (UTC) Received: by mail-vc0-f169.google.com with SMTP id la4so3935390vcb.14 for ; Sun, 15 Jun 2014 06:38:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=2fURErR84UmkulykDjRrkcJvpwsT6D8mDlmeofIo1zo=; b=eXRHgSGQbu0k1XD0LZGQJFeCyEPuFe69UEoc3hgf0qsOLFgzyX2Lom2b6Awq5qNeC5 d+J2GI6c+X3ZvsT45tPNHwM57NKnwIPSAv0MieK3Bk18Z+E40fzGSGxVIMB7oVcX6Bks HG5sWoDuIBC4BaPhgFTkal+bRhY1Gy95CJvSDaJc2/pWE4DDbrQJfZkUJVTnh70D2sVh 12OBRIWHCcoER5eVfqCj4N+OYoInyKH5WwpiNc85w/d+TAc+w7DoH5VZTrvtz71MTM7B 1AXrwYrwpUFwGpNMmGo6cYnWyWwsdW09qR9We/6FPM+4m84mqWP6KDCBLs/9Z+Zfm0XK 2YTQ== MIME-Version: 1.0 X-Received: by 10.221.37.1 with SMTP id tc1mr283977vcb.32.1402839500621; Sun, 15 Jun 2014 06:38:20 -0700 (PDT) Sender: christopher.maness@gmail.com Received: by 10.58.191.35 with HTTP; Sun, 15 Jun 2014 06:38:20 -0700 (PDT) In-Reply-To: <20140615100636.GB23568@slackbox.erewhon.home> References: <20140615022626.7111be2c.freebsd@edvax.de> <20140615100636.GB23568@slackbox.erewhon.home> Date: Sun, 15 Jun 2014 06:38:20 -0700 X-Google-Sender-Auth: bxwW-Cbww62vle9LmJxWIBkTiMA Message-ID: Subject: Re: Port Changes FAQ From: Chris Maness To: Polytropon , Chris Maness , "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Sun, 15 Jun 2014 13:38:22 -0000 Thanks, guys. I like the new pkg (8) command. Will they be recompiling ports whenever they have been patched against vulnerabilities? Chris On Sun, Jun 15, 2014 at 3:06 AM, Roland Smith wrote: > On Sun, Jun 15, 2014 at 02:26:26AM +0200, Polytropon wrote: >> On Sat, 14 Jun 2014 16:53:06 -0700, Chris Maness wrote: >> > I used to use ports, portsnap, portaudit, portupgrade, etc... >> >> No big changes here so far. The system's package database has >> been moved from pkg_* tools to the pkg (pkgng) system, but >> portupgrade or portmaster can deal with that fine. The data >> is now kept in a different database (sqlite). The pkg command >> also has an audit functionality now. >> >> https://wiki.freebsd.org/pkgng >> >> http://www.freebsd.org/cgi/man.cgi?query=pkg&sektion=7 >> >> http://www.freebsd.org/cgi/man.cgi?query=pkg-audit&format=html >> >> Additionally, CVS has been deprecated, so you use SVN to get >> the updates for your local ports tree (or simply use portsnap). > > It seems that portsnap and freebsd-update have certain vulnerabilities that > make it vulnerable to e.g. MITM attacks; > http://lists.freebsd.org/pipermail/freebsd-questions/2014-April/257394.html > > Some PRs have been filed about it as well, e.g; > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188433 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188428 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188430 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188432 > > So unless somebody finds the time to address these, it is not inconceivable > that portsnap will be retired after 8.x and 9.x reach EOL. > > Updating ports with svnlite is easy. Initially do a check-out; > > # rm -rf /usr/ports > # mkdir /usr/ports > # svnlite checkout https://svn0.eu.FreeBSD.org/ports/head /usr/ports > > (I'm using the European mirror as an example. Choose a relatively close mirror.) > > After that you can update the ports tree with; > > # svnlite update /usr/ports |& less > >> > I >> > used to build everything from ports, #make install clean sorts of >> > commands. Is this going away? >> >> It sill works as expected and is still supported. For few >> software, it's the only way of installation because no binary >> package exists (maybe you need specific compile-time options >> which are not the default options). >> >> So far, those are the "big changes" regarding software >> installation: >> >> 1. pkg (instead of pkg_* toolset) >> >> 2. clang (instead of gcc) >> >> 3. Subversion (instead of CVS) > > There is another change coming; the support for installing Python packages for > multiple Python versions. > > Roland > -- > R.F.Smith http://rsmith.home.xs4all.nl/ > [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] > pgp: 5753 3324 1661 B0FE 8D93 FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)