From: Doug McNaught <doug@mcnaught.org>
To: A M <alim1993@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Accessing a process structure in the processes link list
Date: Sun, 28 Nov 2004 18:13:42 -0500 [thread overview]
Message-ID: <874qj9lg7t.fsf@asmodeus.mcnaught.org> (raw)
In-Reply-To: <20041128225720.99389.qmail@web51909.mail.yahoo.com> (A. M.'s message of "Sun, 28 Nov 2004 14:57:20 -0800 (PST)")
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
next prev parent reply other threads:[~2004-11-28 23:13 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 [this message]
2004-11-28 23:37 ` A M
2004-11-28 23:58 ` Jim Nelson
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=874qj9lg7t.fsf@asmodeus.mcnaught.org \
--to=doug@mcnaught.org \
--cc=alim1993@yahoo.com \
--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