From: valdis.kletnieks@vt.edu
To: Namhyung Kim <namhyung.kim@lge.com>
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: Tue, 15 May 2012 15:52:15 -0400 [thread overview]
Message-ID: <52488.1337111535@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 15 May 2012 17:24:11 +0900." <87zk99zwb8.fsf@sejong.aot.lge.com>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
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...
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2012-05-15 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 8:24 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 [this message]
2012-05-16 1:48 ` Namhyung Kim
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=52488.1337111535@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cheol.lee@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung.kim@lge.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®