From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by mail.openembedded.org (Postfix) with ESMTP id 702AE6E672 for ; Wed, 31 May 2017 19:12:53 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.15.2/8.15.1) with ESMTPS id v4VJCrFq003249 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 31 May 2017 12:12:54 -0700 (PDT) Received: from soho-mhatle-m.local (172.25.36.235) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.3.294.0; Wed, 31 May 2017 12:12:53 -0700 To: Cody P Schafer References: <20170530211436.16397-1-dev@codyps.com> <7bed8363-bd79-0233-3e91-1a74f26fca37@windriver.com> From: Mark Hatle Organization: Wind River Systems Message-ID: Date: Wed, 31 May 2017 14:12:52 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Cc: OE-core Subject: Re: [PATCH] runqemu-export-rootfs: don't change RPC ports X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 19:12:54 -0000 Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit On 5/31/17 12:20 PM, Cody P Schafer wrote: >> Non-root user can't create privileged ports. > > I presume you're speaking about tcp/udp ports here? (having the > program numbers referred to as "RPC ports" in some contexts confuses > things). Or does unfsd tell the kernel about it's rpc program numbers > (called "RPC ports" in the script) somehow & restrict them too? > > If it is the first, it isn't clear why that is relevant: I'm not > trying to have unfsd use privileged tcp/udp ports (it's already using > non-privlidged tcp/udp ports). I'm trying to drop the custom rpc > program numbers (which are referred to as "RPC Ports" in the script). > RPC Ports are just the bindings into rpcbind. The tcp/udp ports are the ones that typically conflict and why this was all done to begin with. --Mark