From: Florian Weimer <fweimer@redhat.com>
To: Jim Lieb <jlieb@panasas.com>
Cc: Jeff Layton <jlayton@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: Fixing setfsuid/setfsgid
Date: Thu, 23 Jan 2014 12:28:59 +0100 [thread overview]
Message-ID: <52E0FCFB.8040505@redhat.com> (raw)
In-Reply-To: <5725197.TtPkkAW1pH@jlieb-e6410>
On 01/22/2014 07:21 PM, Jim Lieb wrote:
> I proposed a switch_creds syscall in mid-Oct (a couple of versions).
Got it. The *at-based approach I sketched would achieve roughly the
same thing. I don't know how much glibc will like it if you run your
threads with different effective user IDs, though.
Anyway, this means that for my initial question, adding
getfsuid/getfsgid seems the answer.
--
Florian Weimer / Red Hat Product Security Team
prev parent reply other threads:[~2014-01-23 11:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 12:40 Fixing setfsuid/setfsgid Florian Weimer
2014-01-22 13:56 ` Jeff Layton
2014-01-22 14:06 ` Florian Weimer
2014-01-22 18:21 ` Jim Lieb
2014-01-23 11:28 ` Florian Weimer [this message]
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=52E0FCFB.8040505@redhat.com \
--to=fweimer@redhat.com \
--cc=jlayton@redhat.com \
--cc=jlieb@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).