<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Quick way to find out if you &#8220;ps&#8221; has been compromised</title>
	<atom:link href="http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/</link>
	<description>Ramblings of a hard to follow human being</description>
	<lastBuildDate>Wed, 10 Mar 2010 00:22:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Computing Tips</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-53171</link>
		<dc:creator>Computing Tips</dc:creator>
		<pubDate>Tue, 23 Jun 2009 12:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-53171</guid>
		<description>I found your blog on google and read a few of your other posts. I just added you to my Google News Reader. Keep up the good work. Look forward to reading more from you in the future.</description>
		<content:encoded><![CDATA[<p>I found your blog on google and read a few of your other posts. I just added you to my Google News Reader. Keep up the good work. Look forward to reading more from you in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andre</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-38299</link>
		<dc:creator>Andre</dc:creator>
		<pubDate>Mon, 27 Oct 2008 20:19:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-38299</guid>
		<description>Did you really tried out the command?

ps outpus a header, which give us one more line.

My suggestion would be:

# ls -d /proc/[0-9]* &#124; wc -l; ps -A h &#124; wc -l

My results:
108
108</description>
		<content:encoded><![CDATA[<p>Did you really tried out the command?</p>
<p>ps outpus a header, which give us one more line.</p>
<p>My suggestion would be:</p>
<p># ls -d /proc/[0-9]* | wc -l; ps -A h | wc -l</p>
<p>My results:<br />
108<br />
108</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederico Boaventura</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-38298</link>
		<dc:creator>Frederico Boaventura</dc:creator>
		<pubDate>Mon, 27 Oct 2008 19:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-38298</guid>
		<description>If you use linux colors, try changing the ls command to:

ls --color=none -d /proc/* &#124; grep “[0-9]” &#124; wc-l; ps aux &#124;wc -l

This should fix the difference between the two commands. ;)</description>
		<content:encoded><![CDATA[<p>If you use linux colors, try changing the ls command to:</p>
<p>ls &#8211;color=none -d /proc/* | grep “[0-9]” | wc-l; ps aux |wc -l</p>
<p>This should fix the difference between the two commands. <img src='http://www.andrelop.org/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrelop</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-37346</link>
		<dc:creator>andrelop</dc:creator>
		<pubDate>Sun, 05 Oct 2008 19:32:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-37346</guid>
		<description>@Patricia

Don&#039;t be afraid :-) Just try to find out what&#039;s the culprit. Check my previous answers above and try to get more into details as to why your system is giving you these outputs.

And, as said numerous times before (you guys should read a &quot;maybe&quot; as a &quot;maybe&quot;, not as a &quot;surely it&#039;s like I wrote, no doubt about that&quot;), it could be that it was just a false positive.

There&#039;s no way for me to know what sort of things you guys are running on your systems (operating systems, kernels, softwares, versions, patches, etc) so, I for one would assume that I&#039;m the only who knows more about my specific system/setup than a random Don Joe at the IntarWebs out there :-)

Regards,</description>
		<content:encoded><![CDATA[<p>@Patricia</p>
<p>Don&#8217;t be afraid <img src='http://www.andrelop.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Just try to find out what&#8217;s the culprit. Check my previous answers above and try to get more into details as to why your system is giving you these outputs.</p>
<p>And, as said numerous times before (you guys should read a &#8220;maybe&#8221; as a &#8220;maybe&#8221;, not as a &#8220;surely it&#8217;s like I wrote, no doubt about that&#8221;), it could be that it was just a false positive.</p>
<p>There&#8217;s no way for me to know what sort of things you guys are running on your systems (operating systems, kernels, softwares, versions, patches, etc) so, I for one would assume that I&#8217;m the only who knows more about my specific system/setup than a random Don Joe at the IntarWebs out there <img src='http://www.andrelop.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Regards,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrelop</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-37345</link>
		<dc:creator>andrelop</dc:creator>
		<pubDate>Sun, 05 Oct 2008 19:25:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-37345</guid>
		<description>@Frederico

Well, the command line, exactly as I published it, worked fine on a lot of my personal systems, all of them based on Debian unstable (Linux kernel 2.6.26).

I don&#039;t know if you&#039;re using Debian or even Linux, but as virtually 100% of my readers are aware that I&#039;m a Debian user myself, they should be advised that the command line runs fine on such a system.

BTW, the proposed command line you gave in your comment doesn&#039;t work on any of my Debian unstable systems at all.

First, you have a &quot;wc-l&quot; when it should be &quot;wc -l&quot;. You are lacking a space after the &quot;c&quot; and before the minus signal.

But even fixing this, I still get the following :

andrelop@foolish:~$ ls -d1 /proc/* &#124; grep “[0-9]” &#124; wc -l; ps aux &#124;wc -l
0
125
andrelop@foolish:~$

So, I think my original command line, when executed on a standard Debian unstable system as pointed previsouly, works fine.

Regards,</description>
		<content:encoded><![CDATA[<p>@Frederico</p>
<p>Well, the command line, exactly as I published it, worked fine on a lot of my personal systems, all of them based on Debian unstable (Linux kernel 2.6.26).</p>
<p>I don&#8217;t know if you&#8217;re using Debian or even Linux, but as virtually 100% of my readers are aware that I&#8217;m a Debian user myself, they should be advised that the command line runs fine on such a system.</p>
<p>BTW, the proposed command line you gave in your comment doesn&#8217;t work on any of my Debian unstable systems at all.</p>
<p>First, you have a &#8220;wc-l&#8221; when it should be &#8220;wc -l&#8221;. You are lacking a space after the &#8220;c&#8221; and before the minus signal.</p>
<p>But even fixing this, I still get the following :</p>
<p>andrelop@foolish:~$ ls -d1 /proc/* | grep “[0-9]” | wc -l; ps aux |wc -l<br />
0<br />
125<br />
andrelop@foolish:~$</p>
<p>So, I think my original command line, when executed on a standard Debian unstable system as pointed previsouly, works fine.</p>
<p>Regards,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andrelop</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-37344</link>
		<dc:creator>andrelop</dc:creator>
		<pubDate>Sun, 05 Oct 2008 19:19:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-37344</guid>
		<description>@dudus

As I said previously, this &quot;may&quot; mean your &quot;ps&quot; is compromised. It&#039;s not a clear and indisputable sign that it is really compromised.

I&#039;m not going to tell anyone that one should trust only this small trick to slap a &quot;compromised&quot; stick in one&#039;s system.

You should try to find out which differences you have in these two outputs checking more closely at your /proc and comparing it to your &quot;ps&quot; output to try and find suspicious signs.

Also, checking your &quot;ps&quot; binary mdsum/sha1sum against a know good binary is surely a good thing to do.</description>
		<content:encoded><![CDATA[<p>@dudus</p>
<p>As I said previously, this &#8220;may&#8221; mean your &#8220;ps&#8221; is compromised. It&#8217;s not a clear and indisputable sign that it is really compromised.</p>
<p>I&#8217;m not going to tell anyone that one should trust only this small trick to slap a &#8220;compromised&#8221; stick in one&#8217;s system.</p>
<p>You should try to find out which differences you have in these two outputs checking more closely at your /proc and comparing it to your &#8220;ps&#8221; output to try and find suspicious signs.</p>
<p>Also, checking your &#8220;ps&#8221; binary mdsum/sha1sum against a know good binary is surely a good thing to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patricia</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-37147</link>
		<dc:creator>Patricia</dc:creator>
		<pubDate>Wed, 01 Oct 2008 00:50:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-37147</guid>
		<description>I&#039;m afraid... :/</description>
		<content:encoded><![CDATA[<p>I&#8217;m afraid&#8230; :/</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frederico</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-37092</link>
		<dc:creator>Frederico</dc:creator>
		<pubDate>Mon, 29 Sep 2008 13:29:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-37092</guid>
		<description>There&#039;s something wrong with this command.
I tried it and it game me completely strange results, then I debugged it to:

ls -d1 /proc/* &#124; grep &quot;[0-9]&quot; &#124; wc-l; ps aux &#124;wc -l

This should be correct, &#039;grep&#039; has to have quotes and &#039;ls&#039; default is to show more than one command per line.</description>
		<content:encoded><![CDATA[<p>There&#8217;s something wrong with this command.<br />
I tried it and it game me completely strange results, then I debugged it to:</p>
<p>ls -d1 /proc/* | grep &#8220;[0-9]&#8221; | wc-l; ps aux |wc -l</p>
<p>This should be correct, &#8216;grep&#8217; has to have quotes and &#8216;ls&#8217; default is to show more than one command per line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dudus</title>
		<link>http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/comment-page-1/#comment-37072</link>
		<dc:creator>dudus</dc:creator>
		<pubDate>Mon, 29 Sep 2008 03:06:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.andrelop.org/blog/2008/09/28/quick-way-to-find-out-if-you-ps-has-been-compromised/#comment-37072</guid>
		<description>dudus@dudus-desktop:~$  ls -d /proc/* &#124; grep [0-9] &#124; wc -l ; ps aux &#124; wc -l
185
133

Should I be worried? What do I do to fix that?</description>
		<content:encoded><![CDATA[<p>dudus@dudus-desktop:~$  ls -d /proc/* | grep [0-9] | wc -l ; ps aux | wc -l<br />
185<br />
133</p>
<p>Should I be worried? What do I do to fix that?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
