<?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"
	>
<channel>
	<title>Comments on: Bash socket programming with /dev/tcp</title>
	<atom:link href="http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/</link>
	<description>Your blog is probably better than mine.</description>
	<pubDate>Wed, 19 Nov 2008 04:42:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: David</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-57915</link>
		<dc:creator>David</dc:creator>
		<pubDate>Tue, 16 Sep 2008 01:05:08 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-57915</guid>
		<description>A tad late, but technically all those "\n" should be "\r\n".  The RFC calls for CRLF line termination.</description>
		<content:encoded><![CDATA[<p>A tad late, but technically all those &#8220;\n&#8221; should be &#8220;\r\n&#8221;.  The RFC calls for CRLF line termination.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Craig</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-52892</link>
		<dc:creator>Daniel Craig</dc:creator>
		<pubDate>Wed, 25 Jun 2008 16:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-52892</guid>
		<description>Hey, I was looking around for a while searching for vendor security and I happened upon this site and your post regarding cket programming with /dev/tcp, I will definitely this to my vendor security bookmarks!</description>
		<content:encoded><![CDATA[<p>Hey, I was looking around for a while searching for vendor security and I happened upon this site and your post regarding cket programming with /dev/tcp, I will definitely this to my vendor security bookmarks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Connect-back Shell - Defending the Box &#171; Neohapsis Labs</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-45853</link>
		<dc:creator>Connect-back Shell - Defending the Box &#171; Neohapsis Labs</dc:creator>
		<pubDate>Fri, 18 Apr 2008 20:40:10 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-45853</guid>
		<description>[...] known for quite some time - it&#8217;s easily discovered on the blogosphere in articles here and here for example. Since this is built-in to bash by default in most instances, the main method of [...]</description>
		<content:encoded><![CDATA[<p>[...] known for quite some time - it&#8217;s easily discovered on the blogosphere in articles here and here for example. Since this is built-in to bash by default in most instances, the main method of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-23223</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sun, 22 Jul 2007 14:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-23223</guid>
		<description>I'm afraid I have no idea what you're talking about by "backconnect". Are you talking about the server side?</description>
		<content:encoded><![CDATA[<p>I&#8217;m afraid I have no idea what you&#8217;re talking about by &#8220;backconnect&#8221;. Are you talking about the server side?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-23212</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 22 Jul 2007 08:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-23212</guid>
		<description>can you post the backconnect shellcode?</description>
		<content:encoded><![CDATA[<p>can you post the backconnect shellcode?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Scott</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-20390</link>
		<dc:creator>Ben Scott</dc:creator>
		<pubDate>Sun, 10 Jun 2007 03:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-20390</guid>
		<description>What exactly is the security exposure of the "/dev/tcp/" feature of Bash?  The socket() call will still be available if you disable it.</description>
		<content:encoded><![CDATA[<p>What exactly is the security exposure of the &#8220;/dev/tcp/&#8221; feature of Bash?  The socket() call will still be available if you disable it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-16246</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Thu, 24 May 2007 01:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-16246</guid>
		<description>Thanks, Dave!</description>
		<content:encoded><![CDATA[<p>Thanks, Dave!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-16222</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Wed, 23 May 2007 18:55:44 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-16222</guid>
		<description>Sending a POST with data would be the same, but you would add extra text like this:

echo -e "POST / HTTP/1.1\n\nThis is the body of my POST"&gt;&#038;3

You can also add headers right after the first \n, but be sure to use \n\n before the HTTP body.</description>
		<content:encoded><![CDATA[<p>Sending a POST with data would be the same, but you would add extra text like this:</p>
<p>echo -e &#8220;POST / HTTP/1.1\n\nThis is the body of my POST&#8221;>&#038;3</p>
<p>You can also add headers right after the first \n, but be sure to use \n\n before the HTTP body.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-16221</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 23 May 2007 18:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-16221</guid>
		<description>Dave, can you give an example if I want to send some data to a server, either via GET or POST?

TIA</description>
		<content:encoded><![CDATA[<p>Dave, can you give an example if I want to send some data to a server, either via GET or POST?</p>
<p>TIA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://thesmithfam.org/blog/2006/05/23/bash-socket-programming-with-devtcp-2/#comment-4856</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 27 Jan 2007 19:38:34 +0000</pubDate>
		<guid isPermaLink="false">http://thesmithfam.org/blog/?p=21#comment-4856</guid>
		<description>Eric,

A customer of mine had an immediate need for a small fix to some existing commercial software and hardware on a Red Hat system, to which I had no access. The only thing I knew about the system a priori was that it was Red Hat Enterprise 3. I didn't even know if they had netcat installed or not. I did know, however, that they were running a vanilla install of Red Hat Enterprise. Armed with that knowledge, I was able to solve their problem reliably with a nice, dirty bash hack using /dev/tcp. :)

Had I relied on netcat, it could have come back to me. /dev/tcp did the job for them nicely.</description>
		<content:encoded><![CDATA[<p>Eric,</p>
<p>A customer of mine had an immediate need for a small fix to some existing commercial software and hardware on a Red Hat system, to which I had no access. The only thing I knew about the system a priori was that it was Red Hat Enterprise 3. I didn&#8217;t even know if they had netcat installed or not. I did know, however, that they were running a vanilla install of Red Hat Enterprise. Armed with that knowledge, I was able to solve their problem reliably with a nice, dirty bash hack using /dev/tcp. <img src='http://thesmithfam.org/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Had I relied on netcat, it could have come back to me. /dev/tcp did the job for them nicely.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
