From: Rich Felker <dalias@libc.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: Joshua Hudson <joshudson@gmail.com>,
"musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: Re: posix_spawn
Date: Tue, 1 Oct 2019 10:44:55 -0400 [thread overview]
Message-ID: <20191001144455.GE16318@brightrain.aerifal.cx> (raw)
In-Reply-To: <87muektuud.fsf@oldenburg2.str.redhat.com>
On Tue, Oct 01, 2019 at 04:15:54PM +0200, Florian Weimer wrote:
> * Joshua Hudson:
>
> > You guys open to adding more extensions to posix_spawn?
> >
> > The code that I'm actually trying to run is setgroups;setgid;setuid so
> > I think the use case is common.
> >
> > More of the security-critical code being in the library is generally a
> > good thing.
>
> Rich is objecting to my glibc changes. We require unanimous consent at
> present. Unless I can convince him that his analysis is incorrect, that
> essentially kills further API additions in this area.
Can you point me to which ones you're referring to? I'm not generally
opposed to extensions to solve the deficiencies in posix_spawn, but
there may be one I'm not remembering where there was something about
it in particular that I found problematic.
Rich
next prev parent reply other threads:[~2019-10-01 14:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 21:15 posix_spawn Joshua Hudson
2019-09-30 22:36 ` posix_spawn Rich Felker
2019-10-01 1:58 ` Joshua Hudson
2019-10-01 2:21 ` Rich Felker
2019-10-01 2:41 ` Joshua Hudson
2019-10-01 2:55 ` Rich Felker
2019-10-01 7:05 ` Florian Weimer
2019-10-01 11:42 ` Rich Felker
2019-10-01 14:07 ` posix_spawn Joshua Hudson
2019-10-01 14:15 ` posix_spawn Florian Weimer
2019-10-01 14:44 ` Rich Felker [this message]
2019-10-01 15:06 ` posix_spawn Rich Felker
2019-10-16 12:40 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191001144455.GE16318@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=fweimer@redhat.com \
--cc=joshudson@gmail.com \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).