From: Jim Nelson <james4765@verizon.net>
To: A M <alim1993@yahoo.com>
Cc: Doug McNaught <doug@mcnaught.org>, linux-kernel@vger.kernel.org
Subject: Re: Accessing a process structure in the processes link list
Date: Sun, 28 Nov 2004 18:58:08 -0500 [thread overview]
Message-ID: <41AA6610.7020205@verizon.net> (raw)
In-Reply-To: <20041128233747.53950.qmail@web51902.mail.yahoo.com>
A M wrote:
> How would you know the offset (location of index 0 if
> it was an array or the head of link list) of that
> variable in memory, in this case it is the process
> table named task of type a pointer to task_struct?
>
> Any recommendation for references will be appreciated.
>
>
> Thanks,
>
> Ali
>
http://www.securityfocus.com/infocus/1811
is about identifying hooked syscalls, but the principles involved in locating the
system call table could be applied to finding the process table.
P. S. You can locate the process in memory with read access to /proc/kmem or
/proc/mem (that's a lot tougher, though), but to modify it requires write access.
> --- Doug McNaught <doug@mcnaught.org> wrote:
>
>
>>A M <alim1993@yahoo.com> writes:
>>
>>
>>>Would it be possible for a program running as root
>>>that wasn't compiled with the kernel to access a
>>>process structure in the processes link list?
>>
>>Yes, but see below.
>>
>>
>>>I've read an article about hiding processes and
>>
>>the
>>
>>>article made sound so easy to access the link list
>>
>>and
>>
>>>hide a process, how easy is it?
>>
>>You need read access to /dev/kmem and a fairly
>>intimate knowledge of
>>the kernel data structures in question.
>>
>>
>>>Is it possible to a process to access its own
>>
>>entry in
>>
>>>the processes link list?
>>
>>Not without read access to the kmem device...
>>
>>-Doug
>>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> The all-new My Yahoo! - Get yours free!
> http://my.yahoo.com
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2004-11-28 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 22:57 Accessing a process structure in the processes link list A M
2004-11-28 23:13 ` Doug McNaught
2004-11-28 23:37 ` A M
2004-11-28 23:58 ` Jim Nelson [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=41AA6610.7020205@verizon.net \
--to=james4765@verizon.net \
--cc=alim1993@yahoo.com \
--cc=doug@mcnaught.org \
--cc=linux-kernel@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