

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Syn Fin dot Net &#187; flowreplay</title>
	<atom:link href="http://synfin.net/sock_stream/tag/flowreplay/feed" rel="self" type="application/rss+xml" />
	<link>http://synfin.net/sock_stream</link>
	<description>Streaming Thoughts from Syn to Fin</description>
	<lastBuildDate>Sun, 30 May 2010 03:33:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Flowreplay is dead</title>
		<link>http://synfin.net/sock_stream/news/flowreplay-is-dead</link>
		<comments>http://synfin.net/sock_stream/news/flowreplay-is-dead#comments</comments>
		<pubDate>Wed, 10 Oct 2007 18:22:11 +0000</pubDate>
		<dc:creator>Synfinatic</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[tcpreplay]]></category>
		<category><![CDATA[dead]]></category>
		<category><![CDATA[flowreplay]]></category>

		<guid isPermaLink="false">http://synfin.net/sock_stream/archives/157</guid>
		<description><![CDATA[I&#8217;m officially killing flowreplay as a future feature of tcpreplay.  After giving more thought to this problem and where protocols and applications are going, it&#8217;s become clear to me that the goals of flowreplay are unobtainable.

The basic issue is that protocols/applications are becoming more state based and even so-called stateless protocols like HTTP have [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m officially killing <a href="http://tcpreplay.synfin.net/trac/wiki/flowreplay">flowreplay</a> as a future feature of tcpreplay.  After giving more thought to this problem and where protocols and applications are going, it&#8217;s become clear to me that the goals of flowreplay are unobtainable.<br />
<span id="more-157"></span><br />
The basic issue is that protocols/applications are becoming more state based and even so-called stateless protocols like HTTP have many important stateful characteristics which preclude a tool like flowreplay from properly interacting with a target.  Also more and more protocols are including security features which actively prevent successful replay.</p>
<p>Hence, rather then spending a lot of effort building a custom IP stack and some basic protocol decoders to handle protocols like FTP and SIP, I&#8217;ve decided my relatively limited free time is better spent elsewhere.  With that in mind, I&#8217;ll be removing the flowreplay code from the tcpreplay trunk branch.  If someone/group of people are interested in continuing development of this project, I&#8217;m more then willing to provide hosting and access to the old code, but I&#8217;m unlikely to provide much in the way of assistance.</p>
]]></content:encoded>
			<wfw:commentRss>http://synfin.net/sock_stream/news/flowreplay-is-dead/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->