From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] eal: tighten permissions on shared memory files Date: Thu, 04 Apr 2019 19:51:26 +0200 Message-ID: <38862193.gjzVnSvd9M@xps> References: <20190403160034.31176-1-bruce.richardson@intel.com> <20190403160226.GA1340@bricha3-MOBL.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, anatoly.burakov@intel.com, stable@dpdk.org To: Bruce Richardson Return-path: In-Reply-To: <20190403160226.GA1340@bricha3-MOBL.ger.corp.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 03/04/2019 18:02, Bruce Richardson: > Adding stable@dpdk.org since this is suitable for backporting > > On Wed, Apr 03, 2019 at 05:00:34PM +0100, Bruce Richardson wrote: > > When creating files on disk, e.g. for EAL configuration or shared memory > > locks, etc., there is no need to grant any permissions on those files to > > other users. All directories are already created with 0700 permissions, so > > we should create all files with 0600 permissions. > > > CC: stable@dpdk.org > > Signed-off-by: Bruce Richardson It means the primary and secondary processes must have the same owner. Is it worth to document it? I feel the mask could be an EAL option. Anyway the directories have already a fixed tight mask, so Applied, thanks