From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Eugene Teo <eugeneteo@kernel.sg>
Cc: linux-kernel@vger.kernel.org, "Kawai,
Hidehiro" <hidehiro.kawai.ez@hitachi.com>,
Neil Horman <nhorman@tuxdriver.com>,
Bryan Wu <bryan.wu@analog.com>
Subject: Re: [PATCH 1/3] coredump: cleanup documentation for suid_dumpable
Date: Wed, 1 Aug 2007 13:28:27 +0100 [thread overview]
Message-ID: <20070801132827.355c17e5@the-village.bc.nu> (raw)
In-Reply-To: <46AFF092.6050802@kernel.sg>
> > NAK - this feature is actively used and can be set by the sysctl
> > interface. The PRCTL fixup was just a bug being fixed. The sysctl
> > interface is still relevant.
>
> Thank you for correcting me. Appreciated. I am not aware that it is still
> being actively used. May I know who or which program is using this feature?
Not programs - people.
When you want to debug a large complex system with multiple setuid
applications it can rapidly get quite unpleasant. If you
set /proc/sys/kernel/suid_dumpable to 2 and /proc/sys/kernel/core_pattern
then it becomes possible to get hold of all the core dumps and debug the
system as a whole. The system is not secure in this state but while you
are doing that kind of debug on a devel system its usually acceptable.
Secondly we don't break userspace interfaces except in extreme cases -
proc/sys/kernel/suid_dumpable is a user space interface
Alan
next prev parent reply other threads:[~2007-08-01 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 7:02 [PATCH 0/3] coredump: setuid core dump cleanups Eugene Teo
2007-07-31 7:03 ` [PATCH 1/3] coredump: cleanup documentation for suid_dumpable Eugene Teo
2007-07-31 8:13 ` Alan Cox
2007-08-01 2:31 ` Eugene Teo
2007-08-01 12:28 ` Alan Cox [this message]
2007-07-31 7:04 ` [PATCH 2/3] coredump: remove suidsafe mode related dead code Eugene Teo
2007-07-31 8:14 ` Alan Cox
2007-07-31 7:05 ` [PATCH 3/3] coredump: re-implement suid_dumpable using a flag Eugene Teo
2007-07-31 8:15 ` 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=20070801132827.355c17e5@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bryan.wu@analog.com \
--cc=eugeneteo@kernel.sg \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.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.
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®