From: Chris Wright <chrisw@osdl.org>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, torvalds@osdl.org
Subject: Re: Patch for comment: setuid core dumps
Date: Mon, 27 Sep 2004 14:03:53 -0700 [thread overview]
Message-ID: <20040927140353.Z1973@build.pdx.osdl.net> (raw)
In-Reply-To: <20040927202616.GA22228@devserv.devel.redhat.com>; from alan@redhat.com on Mon, Sep 27, 2004 at 04:26:16PM -0400
* Alan Cox (alan@redhat.com) wrote:
>
> +suid_dumpable:
> +
> +This value can be used to query and set the core dump mode for setuid
> +or otherwise protected/tainted binaries. The modes are
> +
> +0 - (default) - traditional behaviour. Any process which has changed
> + privilege levels or is execute only will not be dumped
> +1 - (debug) - all processes dump core when possible. The core dump is
> + owned by the current user and no security is applied. This is
> + intended for system debugging situations only.
This looks alright, since it keeps 0 and 1 with same meaning (for any
user of prctl).
> +2 - (suidsafe) - any binary which normally not be dumped is dumped
> + readable by root only. This allows the end user to remove
> + such a dump but not access it directly. For security reasons
> + core dumps in this mode will not overwrite one another or
> + other files. This mode is appropriate when adminstrators are
> + attempting to debug problems in a normal environment.
> +
But, in general, did you double check how this plays with /proc
(task_dumpable) and ptrace_attach type stuff? That seems sketchy.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-09-27 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 20:26 Patch for comment: setuid core dumps Alan Cox
2004-09-27 20:37 ` Randy.Dunlap
2004-09-27 21:03 ` Chris Wright [this message]
2004-09-27 21:10 ` Alan Cox
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=20040927140353.Z1973@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=akpm@osdl.org \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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