<?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>Wil Tan &#187; voip</title>
	<atom:link href="http://dready.org/blog/category/voip/feed/" rel="self" type="application/rss+xml" />
	<link>http://dready.org/blog</link>
	<description>musings on internationalized identifiers: domain names, OpenID, TLDs</description>
	<lastBuildDate>Thu, 15 Dec 2011 03:42:26 +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>Skype Reverse-Engineered</title>
		<link>http://dready.org/blog/2006/07/14/skype-reverse-engineered/</link>
		<comments>http://dready.org/blog/2006/07/14/skype-reverse-engineered/#comments</comments>
		<pubDate>Fri, 14 Jul 2006 05:35:36 +0000</pubDate>
		<dc:creator>wil</dc:creator>
				<category><![CDATA[hacks]]></category>
		<category><![CDATA[voip]]></category>

		<guid isPermaLink="false">http://blog.dready.org/2006/07/14/skype-reverse-engineered/</guid>
		<description><![CDATA[VoIPWiki reports that the Skype protocol was successfully cracked by a company in China, who promised to release a demo version by end of August. This is amazing &#8211; not the news itself, but the extent to which they have gone. Several reverse-engineering  reports have been issued but no one has built a working [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.voipwiki.com/blog/?p=16">VoIPWiki</a> reports that the Skype protocol was successfully cracked by a company in China, who promised to release a demo version by end of August. This is amazing &#8211; not the news itself, but the extent to which they have gone. Several <a href="http://www.secdev.org/conf/skype_BHEU06.handout.pdf">reverse-engineering  reports</a> have been issued but no one has built a working prototype until now.</p>
<p>This goes to show that: obfuscation is obfuscation &#8211; it will not last, not if you&#8217;re as popular as Skype.</p>
<p>What does this mean?</p>
<p>Many are predicting / recommending that the eBay company documents its protocol. I can safely say that they will not. This is only news to techies; it may make its way to NYT but people will forget. In fact, as long as it works, they will not lose any market share.</p>
<p>However, it would be great if the Chinese company would publish their findings so that the protocol can be enhanced by others and a more efficient, and certainly open protocol can be created to benefit users.</p>
<p>Think about the 3 main advantages that Skype possesses:<br />
1. Proprietary protocol &#8211; which allows them to have tight control over the evolution of the protocol.</p>
<p>2. Good NAT traversal technology &#8211; this is the main point. This is critical to their success.</p>
<p>3. Good codec &#8211; the GIPS codecs work <b>extremely</b> well. This also ties back to the first point &#8211; they know what codecs their clients can support which is much better what gets negotiated in a heterogenous SIP environment.</p>
<p>It&#8217;s all in the app. Now, I&#8217;d like to see an open source effort is dedicated to making a product work well with the protocol design rather than wasting time trying to obfuscate it!</p>


<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://dready.org/blog/2006/07/14/skype-reverse-engineered/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

