From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Serge Aleynikov <serge@hq.idt.net>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
Alan Cox <alan@redhat.com>
Subject: Re: non-critical security bug fix
Date: Thu, 12 Oct 2006 14:06:47 -0500 [thread overview]
Message-ID: <20061012190647.GA6725@sergelap.austin.ibm.com> (raw)
In-Reply-To: <452D3ED9.509@hq.idt.net>
Quoting Serge Aleynikov (serge@hq.idt.net):
> To Maintainers of the linux/security/commoncap.c:
>
> Patch description:
> ==================
> This bug-fix ensures that if a process with root access sets
> keep_capabilities flag, current capabilities get preserved when the
> process switches from root to another effective user. It looks like
> this was intended from the way capabilities are documented, but the
> current->keep_capabilities flag is not being checked.
Note that without your patch, the permitted set is maintained, so that
you can regain the caps into your effective set after setuid if you
need. i.e.
prctl(PR_SET_KEEPCAPS, 1);
setresuid(1000, 1000, 1000);
caps = cap_from_text("cap_net_admin,cap_sys_admin,cap_dac_override=ep");
ret = cap_set_proc(caps);
So this patch will change the default behavior, but does not add
features or change what is possible.
Ordinarely I'd say changing default behavior wrt security is a bad
thing, but given that this is "default behavior when doing prctl(PR_SET_KEEPCAPS)",
I don't know how much it matters.
Still, I like the current behavior, where setuid means drop effective
caps no matter what.
-serge
next prev parent reply other threads:[~2006-10-12 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 18:58 Serge Aleynikov
2006-10-12 19:06 ` Serge E. Hallyn [this message]
2006-10-12 19:25 ` Serge Aleynikov
2006-10-12 20:29 ` Serge E. Hallyn
2006-10-12 21:11 ` Serge Aleynikov
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=20061012190647.GA6725@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serge@hq.idt.net \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®