From: Doug McNaught <doug@mcnaught.org>
To: mru@kth.se (Måns Rullgård)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Rootkit queston
Date: Sat, 06 Dec 2003 10:10:18 -0500 [thread overview]
Message-ID: <87ad66ugmd.fsf@asmodeus.mcnaught.org> (raw)
In-Reply-To: <yw1x65gu7zy7.fsf@kth.se> ( Måns Rullgård's message of "Sat, 06 Dec 2003 16:01:20 +0100")
mru@kth.se (Måns Rullgård) writes:
> Suppose you found a bug in a web server that would make the server
> append arbitrary data to existing files. Adding that line to
> inetd.conf would be one way to use that bug to gain full control over
> the machine.
But the inetd.conf line itself isn't an "attack"; it's a backdoor put
in after an attack is successful.
Just terminology... :)
-Doug
next prev parent reply other threads:[~2003-12-06 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-06 13:45 [OT] Rootkit queston Samium Gromoff
2003-12-06 15:01 ` Måns Rullgård
2003-12-06 15:10 ` Doug McNaught [this message]
2003-12-06 15:07 ` Christian
2003-12-08 13:49 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 21:24 Albert Cahalan
2003-12-01 21:11 Markus Hästbacka
2003-12-01 22:19 ` Richard B. Johnson
2003-12-01 23:36 ` Måns Rullgård
2003-12-01 23:47 ` Mike Fedyk
2003-12-01 22:48 ` Bernd Eckenfels
2003-12-05 17:29 ` dean gaudet
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=87ad66ugmd.fsf@asmodeus.mcnaught.org \
--to=doug@mcnaught.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/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