[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 13 Oct 2020 17:49:11 +0200
From: Florian Weimer <fweimer@...hat.com>
To: Rich Felker <dalias@...c.org>
Cc: libc-coord@...ts.openwall.com, Ariadne Conill <ariadne@...eferenced.org>
Subject: Re: [RFC] Add posix_spawnattr_chroot_np()
* 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.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
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.
