From: Namhyung Kim <namhyung.kim@lge.com>
To: valdis.kletnieks@vt.edu
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
linux-kernel@vger.kernel.org, Hyeoncheol Lee <cheol.lee@lge.com>
Subject: Re: [QUESTION] Kprobes as a module?
Date: Wed, 16 May 2012 10:48:06 +0900 [thread overview]
Message-ID: <871umkew15.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <52488.1337111535@turing-police.cc.vt.edu> (valdis kletnieks's message of "Tue, 15 May 2012 15:52:15 -0400")
Hi,
On Tue, 15 May 2012 15:52:15 -0400, valdis kletnieks wrote:
> On Tue, 15 May 2012 17:24:11 +0900, Namhyung Kim said:
>> Probably a dumb question :).
>> What prevents the kprobes from being built as a module? We want to use
>> the kprobes on our systems, but some guys worried about potential
>> security problems. So it'd be great if we can enable/load kprobes as
>> needed and then disable/unload after using it. Is it a possible senario?
>
> Any troublemaker who has the ability to set a kprobe would probably also
> have theability to just re-load the module before setting the kprobe (unless
> you go to a *lot* of trouble to compartmentalize the root user).
>
> So it's not clear there's a security benefit from making it a module. If anything,
> it makes it *worse* because you can then surprise a sysadmin who *thought*
> they were running a KPROBES=n kernel by loading a module and turning it on...
Right, thanks for your comment.
Namhyung
prev parent reply other threads:[~2012-05-16 1:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 8:24 [QUESTION] Kprobes as a module? Namhyung Kim
2012-05-15 8:31 ` Cong Wang
2012-05-15 8:34 ` Namhyung Kim
2012-05-15 12:18 ` Masami Hiramatsu
2012-05-16 1:44 ` Namhyung Kim
2012-05-15 19:52 ` valdis.kletnieks
2012-05-16 1:48 ` Namhyung Kim [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=871umkew15.fsf@sejong.aot.lge.com \
--to=namhyung.kim@lge.com \
--cc=cheol.lee@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=valdis.kletnieks@vt.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.