<?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: .tivo file format</title>
	<atom:link href="http://www.outflux.net/blog/archives/2005/02/25/tivo-file-format/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.outflux.net/blog/archives/2005/02/25/tivo-file-format/</link>
	<description>code is freedom -- patching my itch</description>
	<pubDate>Tue, 06 Jan 2009 09:27:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: codeblog &#187; pattern visualization</title>
		<link>http://www.outflux.net/blog/archives/2005/02/25/tivo-file-format/#comment-46</link>
		<dc:creator>codeblog &#187; pattern visualization</dc:creator>
		<pubDate>Thu, 14 Jul 2005 02:59:37 +0000</pubDate>
		<guid isPermaLink="false">http://outflux.net/blog/archives/2005/02/25/tivo-file-format/#comment-46</guid>
		<description>[...] So, frequently, I&#8217;m faced with streams of bytes of unknown origin/purpose. (For example, the .TiVo file format, RTMP streams, and most recently, Outlook &#8220;NK2&#8243; address autocompletion cache files.) I&#8217;ve had experience finding patterns, but it&#8217;s always so time-consuming. Usually I&#8217;m compiling some little C program over and over, slowly tweaking some guessed-at structure. This is basically the advice I got from Andrew Tridgell when I asked how he went about reverse engineering protocols. His methods deal more with sending/receiving, so it&#8217;s much more interactive. Most of what I&#8217;ve mucked with are just unknown file formats. [...]</description>
		<content:encoded><![CDATA[<p>[...] So, frequently, I&#8217;m faced with streams of bytes of unknown origin/purpose. (For example, the .TiVo file format, RTMP streams, and most recently, Outlook &#8220;NK2&#8243; address autocompletion cache files.) I&#8217;ve had experience finding patterns, but it&#8217;s always so time-consuming. Usually I&#8217;m compiling some little C program over and over, slowly tweaking some guessed-at structure. This is basically the advice I got from Andrew Tridgell when I asked how he went about reverse engineering protocols. His methods deal more with sending/receiving, so it&#8217;s much more interactive. Most of what I&#8217;ve mucked with are just unknown file formats. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
