Dr. Dobb's is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Channels ▼
RSS

File Recovery Techniques


Dec00: Case Study: rootkit

Case Study: rootkit

To find out how robust deleted file information can be, I set up a disposable RedHat 5.2 Linux machine and downloaded Version 4 of the Linux rootkit source distribution. The rootkit software produces a network password sniffer program and replaces over a dozen system utilities with modified versions that either reveal intruder activity or provide intruder backdoors. I compiled, installed, and removed the rootkit software, just like an intruder.

Then I did just about the worst possible thing. I downloaded the Coroner's Toolkit source distribution, unpacked it in the same directory as used by the "intruder," compiled it, and ran the software. (To avoid data destruction as described here, we intend to make ready-to-run CD-ROM images available.)

Using the Coroner's Toolkit in this manner, I knowingly destroyed large amounts of information by overwriting deleted files and obliterating file access time information for compiler-related files and for other files.

Even after all that destruction, the Coroner's Toolkit still found useful information. Access time patterns of deleted files revealed that at least 460 files and directories were created and deleted within a relatively short amount of time. At least 300 of those files had practically identical last modification times on November 23, 1998, the apparent time when Linux rootkit Version 4 was prepared for distribution.

The signatures from deleted file attributes were so strong because intruder software suffers from bloat just like any other software. Linux rootkit Version 4 has a rather large footprint of approximately 780 files and directories, including compiler output files. A footprint that large is hard to overlook, even in deleted file access time patterns.

-- W.V.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.