From owner-freebsd-ports@FreeBSD.ORG Fri Oct 4 21:45:37 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6E2092E0 for ; Fri, 4 Oct 2013 21:45:37 +0000 (UTC) (envelope-from prvs=982df0aff=pschmehl_lists@tx.rr.com) Received: from ip-001.utdallas.edu (ip-001.utdallas.edu [129.110.180.40]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 370A42899 for ; Fri, 4 Oct 2013 21:45:36 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiMFADs2T1KBbgogUmdsb2JhbABZhnOuCpIaAwEXBBIHPIJkAjqBKRqIGZsPhwCaNpJ3gQQDiTmZBIsFHg X-IPAS-Result: AiMFADs2T1KBbgogUmdsb2JhbABZhnOuCpIaAwEXBBIHPIJkAjqBKRqIGZsPhwCaNpJ3gQQDiTmZBIsFHg X-IronPort-AV: E=Sophos;i="4.90,1035,1371099600"; d="scan'208";a="7213200" Received: from zxtm01.utdallas.edu (HELO utd71538.utdallas.edu) ([129.110.10.32]) by ip-001.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Oct 2013 16:45:35 -0500 Date: Fri, 04 Oct 2013 16:45:34 -0500 From: Paul Schmehl To: FreeBSD Ports Subject: NEED_ROOT Message-ID: <3D9FA771C2C9D44964566658@localhost> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=968 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Paul Schmehl List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Oct 2013 21:45:37 -0000 >From my reading it appears that one of the goals of STAGE is to allow users to build and install ports under their UID. Are the perms in /usr/ports changing? In testing the port that I'm working on, I find that I do not have rights to write to /usr/ports/distfiles and I do not have rights to write to ${WORKDIR}. That pretty much precludes building the port unless your root. No surprise there since the files in /usr/ports are owned by root:wheel. So are the perms going to change? Is port building going to run setuid? Or is this a vaporware? -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell