Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201013160938.GR17637@brightrain.aerifal.cx>
Date: Tue, 13 Oct 2020 12:09:38 -0400
From: Rich Felker <dalias@...c.org>
To: Florian Weimer <fweimer@...hat.com>
Cc: libc-coord@...ts.openwall.com,
	Ariadne Conill <ariadne@...eferenced.org>
Subject: Re: [RFC] Add posix_spawnattr_chroot_np()

On Tue, Oct 13, 2020 at 05:49:11PM +0200, Florian Weimer wrote:
> * Rich Felker:
> 
> > I don't like that this is storing unbounded-size state in the
> > attribute object, and the obvious solution to the first question (and
> > the second) is that chroot should not be an attribute but a file
> > action, the same way chdir (newly added) is.
> 
> I think a chroot action should be interspersed with other file actions,
> so that file action are impacted by it.  For example, it enables
> subsequent open actions to rely on the lookup-constraining properties of
> chroot.  That's why I think it's useful.

Right, that's what I meant by saying it should be a file action --
that it should be executed in the normal sequence of file actions
according to the order they were added.

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.