<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rootkit on scarbrough.co.uk</title>
    <link>/tags/rootkit/</link>
    <description>Recent content in Rootkit on scarbrough.co.uk</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 05 May 2012 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/rootkit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux Rootkit Case Study Notes</title>
      <link>/post/security/linux-rootkit-case-study/</link>
      <pubDate>Sat, 05 May 2012 00:00:00 +0000</pubDate>
      <guid>/post/security/linux-rootkit-case-study/</guid>
      <description>!!! info Original post on my WordPress site&#xA;The Scenario The following is a summary of what’s presented in the case study. It begins with the discovery of the following in file inetd.conf on a workstation running Red Hat Linux:&#xA;netstat stream tcp nowait root /usr/lib/netstat netstat A graphical CPU load monitor showed 100% load, the top command indicated only 90%, and there were apparently no running processes listed that accounted for the discrepancy.</description>
    </item>
  </channel>
</rss>
