From: Alexey Dobriyan <adobriyan@gmail.com>
To: wzt wzt <wzt.wzt@gmail.com>
Cc: linux-kernel@vger.kernel.org, sds@tycho.nsa.gov,
jmorris@namei.org, eparis@parisplace.org
Subject: Re: [PATCH] LSM: add static to security_ops variable
Date: Fri, 19 Feb 2010 14:27:14 +0200 [thread overview]
Message-ID: <b6fcc0a1002190427k735dc6a8ha88cb79b4d333c3e@mail.gmail.com> (raw)
In-Reply-To: <628d1651002190423s4590bbc5x2eeff6792619f591@mail.gmail.com>
On Fri, Feb 19, 2010 at 2:23 PM, wzt wzt <wzt.wzt@gmail.com> wrote:
>> It's not a barrier, it's garbage. Once you know the adress security_ops
>> ended up at, you simply write to it.
>
> How to find the security_ops address if the variable is static? Would
> you please make an example?
See /proc/kallsyms .
>> Not that easily, but they still can.
> That's why i suggest to make the variable to static, if you had wrote
> a rootkit, you will find that in kernel 2.4.x, there are many many
> rootkits, but in kernel 2.6.x, rootkit became fewer. Not all the
> kernel driver writers can master this method to find the variable's
> address.
Please.
> The patch also delete the secondary_ops variable.
next prev parent reply other threads:[~2010-02-19 12:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 11:24 wzt wzt
2010-02-07 14:14 ` Greg KH
2010-02-16 14:57 ` Stephen Smalley
2010-02-19 11:40 ` wzt wzt
2010-02-19 13:47 ` Stephen Smalley
2010-02-19 11:44 ` Alexey Dobriyan
2010-02-19 11:57 ` wzt wzt
2010-02-19 12:02 ` Alexey Dobriyan
2010-02-19 12:23 ` wzt wzt
2010-02-19 12:27 ` Alexey Dobriyan [this message]
2010-02-19 13:14 ` wzt wzt
2010-02-19 13:12 ` Bernd Petrovitsch
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=b6fcc0a1002190427k735dc6a8ha88cb79b4d333c3e@mail.gmail.com \
--to=adobriyan@gmail.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=wzt.wzt@gmail.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®