From: Kees Cook <kees.cook@canonical.com>
To: linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Yama: add PTRACE exception tracking
Date: Tue, 29 Jun 2010 17:38:44 -0700 [thread overview]
Message-ID: <20100630003844.GE4837@outflux.net> (raw)
The primary exception to Yama's descendant-based PTRACE restrictions
is when an application has a predefined crash handler that is spawned
in parallel with the crashed application (e.g. KDE, Chromium). These
applications want to bypass the common RLIMIT_CORE=0, and gather state
information from the process for upstream problem reporting. When the
main application crashes, it generally has access to the PID of what
will debug it (e.g. when a KDE app crashes, it knows the parent PID of
the debugger that will be spawned).
So, since this programmatic method of PTRACEing is useful, there should be
a way for processes to actively declare who can PTRACE them. This patch
adds a prctl hook for Yama so that processes can exempt themselves from
the PTRACE restrictions in the case of a crash when they know their
debugger's PID.
As a matter of demonstration, here is what the patch to KDE4 would look
like to support Yama, or other PTRACE-restricting LSMs that wanted to grant
a similar exception:
--- kde4libs-4.4.90.orig/kdeui/util/kcrash.cpp 2010-06-28 17:07:28.667869954 -0700
+++ kde4libs-4.4.90/kdeui/util/kcrash.cpp 2010-06-28 17:09:32.089958401 -0700
@@ -41,6 +41,7 @@
#include <sys/wait.h>
#include <sys/un.h>
#include <sys/socket.h>
+#include <sys/prctl.h>
#include <errno.h>
#include <qwindowdefs.h>
@@ -437,6 +438,7 @@
//if the process was started directly, use waitpid(), as it's a child...
while(waitpid(-1, NULL, 0) != pid) {}
} else {
+ prctl(PR_SET_PTRACER, pid, 0, 0, 0);
//...else poll its status using kill()
while(kill(pid, 0) >= 0) {
sleep(1);
--
Kees Cook
Ubuntu Security Team
next reply other threads:[~2010-06-30 0:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 0:38 Kees Cook [this message]
2010-06-30 0:39 ` [PATCH 1/2] security: create task_free security callback Kees Cook
2010-06-30 0:40 ` [PATCH 2/2] Yama: add PTRACE exception tracking Kees Cook
2010-06-30 1:09 ` Tetsuo Handa
2010-06-30 3:51 ` Kees Cook
2010-06-30 3:56 ` Serge E. Hallyn
2010-06-30 5:27 ` Kees Cook
2010-06-30 12:40 ` Serge E. Hallyn
2010-06-30 15:41 ` Eric Paris
2010-06-30 15:53 ` Kees Cook
2010-06-30 21:39 ` Tetsuo Handa
2010-06-30 7:31 ` [PATCH 0/2] " Christoph Hellwig
2010-06-30 15:45 ` Kees Cook
2010-07-01 1:39 ` James Morris
2010-07-01 4:44 ` Kees Cook
2010-07-01 13:20 ` Serge E. Hallyn
2010-07-01 15:22 ` Stephen Smalley
2010-07-01 17:16 ` Kees Cook
2010-07-01 19:41 ` Serge E. Hallyn
2010-07-01 19:57 ` Stephen Smalley
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=20100630003844.GE4837@outflux.net \
--to=kees.cook@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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
Powered by JetHome