From: Florian Weimer <fweimer@redhat.com>
To: Boaz Harrosh <openosd@gmail.com>,
Jeff Layton <jlayton@redhat.com>, Jim Lieb <jlieb@panasas.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
LSM List <linux-security-module@vger.kernel.org>,
"Serge E. Hallyn" <serge@canonical.com>,
Kees Cook <keescook@chromium.org>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
bfields@redhat.com
Subject: Re: Thoughts on credential switching
Date: Tue, 22 Apr 2014 13:37:53 +0200 [thread overview]
Message-ID: <53565491.702@redhat.com> (raw)
In-Reply-To: <533428BF.8090007@gmail.com>
On 03/27/2014 02:33 PM, Boaz Harrosh wrote:
> man setuid should be saying DEPRECATED, EMULATED and SIGNAL NOT SAFE
> and be done with it POSIX or no POSIX who cares?
The glibc side cares, and there's also this bit: "It aims towards POSIX
and Single UNIX Specification compliance.", which should be familiar.
I get that POSIX doesn't do what people want here (umask and current
directory handling are another story). But it hasn't really helped that
some folks just said "POSIX sucks" and did their own thing, completely
bypassing the system interfaces, instead of getting things fixed
properly. Now we have to balance the kernel behavior, POSIX demands,
glibc dirty hacks to implement the questionable POSIX behavior on top of
the kernel interfaces, and more dirty hacks to work around glibc because
some applications do not like it.
I would really like to clean up this mess, but it's not clear to me
where to start.
> Please show me one user of that and declare it brain dead.
Safely and demonstratively relinquishing elevated privileges.
> POSIX or not it just does not have any real programming mining
> at all.
What do you mean with "mining" in this context?
--
Florian Weimer / Red Hat Product Security Team
next prev parent reply other threads:[~2014-04-22 11:38 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 0:23 Thoughts on credential switching Andy Lutomirski
2014-03-27 0:42 ` Serge Hallyn
2014-03-27 1:01 ` Andy Lutomirski
2014-03-27 15:41 ` Florian Weimer
2014-03-27 16:21 ` Andy Lutomirski
2014-03-27 2:48 ` Jeff Layton
2014-03-27 3:05 ` Andy Lutomirski
2014-03-27 3:25 ` Jeff Layton
2014-03-27 14:08 ` Jeff Layton
2014-03-29 6:43 ` Alex Elsayed
2014-03-30 13:03 ` Theodore Ts'o
2014-03-30 18:56 ` Andy Lutomirski
2014-03-31 11:51 ` Jeff Layton
2014-03-31 18:06 ` Trond Myklebust
2014-03-31 18:12 ` Jeff Layton
2014-03-31 19:26 ` Andy Lutomirski
2014-03-31 20:14 ` Trond Myklebust
2014-03-31 21:25 ` Andy Lutomirski
2014-03-27 12:46 ` Florian Weimer
2014-03-27 13:02 ` Jeff Layton
2014-03-27 13:06 ` Florian Weimer
2014-03-27 13:33 ` Boaz Harrosh
2014-04-22 11:37 ` Florian Weimer [this message]
2014-04-22 12:14 ` Boaz Harrosh
2014-04-22 16:35 ` Jim Lieb
2014-03-27 14:01 ` Jeff Layton
2014-03-27 18:26 ` Jeremy Allison
2014-03-27 18:46 ` Andy Lutomirski
2014-03-27 18:56 ` Jeremy Allison
2014-03-27 19:02 ` Andy Lutomirski
2014-03-27 19:30 ` Jim Lieb
2014-03-27 19:45 ` Andy Lutomirski
2014-03-27 20:47 ` Jim Lieb
2014-03-27 21:19 ` Andy Lutomirski
2014-03-31 10:44 ` One Thousand Gnomes
2014-03-31 16:49 ` Andy Lutomirski
2014-04-01 20:22 ` One Thousand Gnomes
2014-03-31 19:05 ` Jeremy Allison
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=53565491.702@redhat.com \
--to=fweimer@redhat.com \
--cc=bfields@redhat.com \
--cc=ebiederm@xmission.com \
--cc=jlayton@redhat.com \
--cc=jlieb@panasas.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=openosd@gmail.com \
--cc=serge@canonical.com \
--cc=tytso@mit.edu \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox