<?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: Things that make you go hmmmm &#8211; Final Thoughts on the ESX/ESXi 3.5 Update 2 Bug</title>
	<atom:link href="http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Wed, 25 Jan 2012 13:41:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Rich</title>
		<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/comment-page-1/#comment-1029</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Sat, 16 Aug 2008 02:32:42 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=584#comment-1029</guid>
		<description>Ben,

I guess I misunderstood your point the first time. Your logic makes sense, and like I said before I understand your points about how the paying customer suffers. But after re-reading both your comments now I&#039;m not sure how you even came to the idea that VMware&#039;s time bomb was implemented to protect from piracy. Paul Maritz explained in his blog post:

&quot;This piece of code was left over from the pre-release versions of Update 2 and was designed to ensure that customers are running on the supported generally available version of Update 2.&quot;

I don&#039;t take that to mean they were focused on stopping theft, but instead wanted to guarantee a bug free version was generally available and in use. That&#039;s more about VMware having to support their customers and making sure their help desk infrastructure gets calls about the correct builds. It makes the whole issue more ironic, I know, but in my mind it is an acceptable development and product release process. It&#039;s definitely unacceptable QA testing to leave it enabled, however.</description>
		<content:encoded><![CDATA[<p>Ben,</p>
<p>I guess I misunderstood your point the first time. Your logic makes sense, and like I said before I understand your points about how the paying customer suffers. But after re-reading both your comments now I&#8217;m not sure how you even came to the idea that VMware&#8217;s time bomb was implemented to protect from piracy. Paul Maritz explained in his blog post:</p>
<p>&#8220;This piece of code was left over from the pre-release versions of Update 2 and was designed to ensure that customers are running on the supported generally available version of Update 2.&#8221;</p>
<p>I don&#8217;t take that to mean they were focused on stopping theft, but instead wanted to guarantee a bug free version was generally available and in use. That&#8217;s more about VMware having to support their customers and making sure their help desk infrastructure gets calls about the correct builds. It makes the whole issue more ironic, I know, but in my mind it is an acceptable development and product release process. It&#8217;s definitely unacceptable QA testing to leave it enabled, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/comment-page-1/#comment-5333</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Sat, 16 Aug 2008 02:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=584#comment-5333</guid>
		<description>Ben,

I guess I misunderstood your point the first time. Your logic makes sense, and like I said before I understand your points about how the paying customer suffers. But after re-reading both your comments now I&#039;m not sure how you even came to the idea that VMware&#039;s time bomb was implemented to protect from piracy. Paul Maritz explained in his blog post:

&quot;This piece of code was left over from the pre-release versions of Update 2 and was designed to ensure that customers are running on the supported generally available version of Update 2.&quot;

I don&#039;t take that to mean they were focused on stopping theft, but instead wanted to guarantee a bug free version was generally available and in use. That&#039;s more about VMware having to support their customers and making sure their help desk infrastructure gets calls about the correct builds. It makes the whole issue more ironic, I know, but in my mind it is an acceptable development and product release process. It&#039;s definitely unacceptable QA testing to leave it enabled, however.</description>
		<content:encoded><![CDATA[<p>Ben,</p>
<p>I guess I misunderstood your point the first time. Your logic makes sense, and like I said before I understand your points about how the paying customer suffers. But after re-reading both your comments now I&#8217;m not sure how you even came to the idea that VMware&#8217;s time bomb was implemented to protect from piracy. Paul Maritz explained in his blog post:</p>
<p>&#8220;This piece of code was left over from the pre-release versions of Update 2 and was designed to ensure that customers are running on the supported generally available version of Update 2.&#8221;</p>
<p>I don&#8217;t take that to mean they were focused on stopping theft, but instead wanted to guarantee a bug free version was generally available and in use. That&#8217;s more about VMware having to support their customers and making sure their help desk infrastructure gets calls about the correct builds. It makes the whole issue more ironic, I know, but in my mind it is an acceptable development and product release process. It&#8217;s definitely unacceptable QA testing to leave it enabled, however.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Pottinger</title>
		<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/comment-page-1/#comment-1026</link>
		<dc:creator>Ben Pottinger</dc:creator>
		<pubDate>Fri, 15 Aug 2008 18:51:09 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=584#comment-1026</guid>
		<description>I&#039;m not sure I follow your disagreement.  I never suggested working for free.  Just use a simple license key setup without a &quot;kill switch&quot; or activation.  If you need to sue a company/user for theft of your software, the difficultly of stealing it is immaterial.  Its stolen regardless if all you had to do was copy the DVD using nero or if you had to spend 500 hours cracking the protection scheme.

the problem happens when you attempt to actually &quot;stop&quot; the pirating by making the copy protection scheme really complex and difficult.  #1 you don&#039;t actually slow the pirates down (like I said, just check torrent, heck they already hacked bluray and HDDVD) and #2, the harder the protection scheme is the bigger a problem it becomes for your PAYING customer.

Adobe and Microsoft&#039;s activation schemes have gotten so bad its forcing some people to look at different products.

Basically, all I&#039;m saying is a bug that causes the kind of problem sucks.  A bug that causes this kind of problem related to the licensing of the product is unacceptable.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I follow your disagreement.  I never suggested working for free.  Just use a simple license key setup without a &#8220;kill switch&#8221; or activation.  If you need to sue a company/user for theft of your software, the difficultly of stealing it is immaterial.  Its stolen regardless if all you had to do was copy the DVD using nero or if you had to spend 500 hours cracking the protection scheme.</p>
<p>the problem happens when you attempt to actually &#8220;stop&#8221; the pirating by making the copy protection scheme really complex and difficult.  #1 you don&#8217;t actually slow the pirates down (like I said, just check torrent, heck they already hacked bluray and HDDVD) and #2, the harder the protection scheme is the bigger a problem it becomes for your PAYING customer.</p>
<p>Adobe and Microsoft&#8217;s activation schemes have gotten so bad its forcing some people to look at different products.</p>
<p>Basically, all I&#8217;m saying is a bug that causes the kind of problem sucks.  A bug that causes this kind of problem related to the licensing of the product is unacceptable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Pottinger</title>
		<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/comment-page-1/#comment-5332</link>
		<dc:creator>Ben Pottinger</dc:creator>
		<pubDate>Fri, 15 Aug 2008 18:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=584#comment-5332</guid>
		<description>I&#039;m not sure I follow your disagreement.  I never suggested working for free.  Just use a simple license key setup without a &quot;kill switch&quot; or activation.  If you need to sue a company/user for theft of your software, the difficultly of stealing it is immaterial.  Its stolen regardless if all you had to do was copy the DVD using nero or if you had to spend 500 hours cracking the protection scheme.

the problem happens when you attempt to actually &quot;stop&quot; the pirating by making the copy protection scheme really complex and difficult.  #1 you don&#039;t actually slow the pirates down (like I said, just check torrent, heck they already hacked bluray and HDDVD) and #2, the harder the protection scheme is the bigger a problem it becomes for your PAYING customer.

Adobe and Microsoft&#039;s activation schemes have gotten so bad its forcing some people to look at different products.

Basically, all I&#039;m saying is a bug that causes the kind of problem sucks.  A bug that causes this kind of problem related to the licensing of the product is unacceptable.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I follow your disagreement.  I never suggested working for free.  Just use a simple license key setup without a &#8220;kill switch&#8221; or activation.  If you need to sue a company/user for theft of your software, the difficultly of stealing it is immaterial.  Its stolen regardless if all you had to do was copy the DVD using nero or if you had to spend 500 hours cracking the protection scheme.</p>
<p>the problem happens when you attempt to actually &#8220;stop&#8221; the pirating by making the copy protection scheme really complex and difficult.  #1 you don&#8217;t actually slow the pirates down (like I said, just check torrent, heck they already hacked bluray and HDDVD) and #2, the harder the protection scheme is the bigger a problem it becomes for your PAYING customer.</p>
<p>Adobe and Microsoft&#8217;s activation schemes have gotten so bad its forcing some people to look at different products.</p>
<p>Basically, all I&#8217;m saying is a bug that causes the kind of problem sucks.  A bug that causes this kind of problem related to the licensing of the product is unacceptable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/comment-page-1/#comment-1025</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Fri, 15 Aug 2008 16:20:33 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=584#comment-1025</guid>
		<description>Ben,

You bring up some good points about how the damage can be done to the one&#039;s that need to be protected. However, I can&#039;t blame VMware, Microsoft, or any company for wanting it&#039;s customers to buy licenses and pay for support, and then enforcing it. Do you work for free? 

Your argument that it&#039;s an inconvenience for paying customers and it&#039;s easy for a pirate to crack anyways won&#039;t exactly protect your &quot;booty&quot; in court!</description>
		<content:encoded><![CDATA[<p>Ben,</p>
<p>You bring up some good points about how the damage can be done to the one&#8217;s that need to be protected. However, I can&#8217;t blame VMware, Microsoft, or any company for wanting it&#8217;s customers to buy licenses and pay for support, and then enforcing it. Do you work for free? </p>
<p>Your argument that it&#8217;s an inconvenience for paying customers and it&#8217;s easy for a pirate to crack anyways won&#8217;t exactly protect your &#8220;booty&#8221; in court!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/comment-page-1/#comment-5331</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Fri, 15 Aug 2008 16:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=584#comment-5331</guid>
		<description>Ben,

You bring up some good points about how the damage can be done to the one&#039;s that need to be protected. However, I can&#039;t blame VMware, Microsoft, or any company for wanting it&#039;s customers to buy licenses and pay for support, and then enforcing it. Do you work for free? 

Your argument that it&#039;s an inconvenience for paying customers and it&#039;s easy for a pirate to crack anyways won&#039;t exactly protect your &quot;booty&quot; in court!</description>
		<content:encoded><![CDATA[<p>Ben,</p>
<p>You bring up some good points about how the damage can be done to the one&#8217;s that need to be protected. However, I can&#8217;t blame VMware, Microsoft, or any company for wanting it&#8217;s customers to buy licenses and pay for support, and then enforcing it. Do you work for free? </p>
<p>Your argument that it&#8217;s an inconvenience for paying customers and it&#8217;s easy for a pirate to crack anyways won&#8217;t exactly protect your &#8220;booty&#8221; in court!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Pottinger</title>
		<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/comment-page-1/#comment-1024</link>
		<dc:creator>Ben Pottinger</dc:creator>
		<pubDate>Fri, 15 Aug 2008 15:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=584#comment-1024</guid>
		<description>What I noticed about this whole ordeal is that it all started as a licensing issue.  You also posted about another licensing bug recently:
http://vmetc.com/2008/01/25/esx-35-4-socket-host-based-license-patch/

Both of these issues I think underscore a major problem in the PC industry and its the near psychotic need to implement draconian protection schemes.  The pirates have proven what a waste of time such schemes are (you often see popular software on torrent before its available in the store, all pre-cracked and ready to use).  It doesn&#039;t even seem to slow them down most of the time.  Instead all it does is inconvenience and sometimes severely damage the paying customer!  

VMware&#039;s comment about &quot;no licensing backdoor&quot; shows they are more concerned with protecting their (faulty) licensing scheme then protecting their enterprise customers.  Its even more baffling when you consider the niche this product fills.  It&#039;s not exactly a mass market piece of software that needs to fend off the causal pirate.  How many organizations would really be running a pirate copy of a 5,000$ piece of software?

I&#039;m just waiting for the evidential shift to microsoft/adobe style &quot;activation&quot;.</description>
		<content:encoded><![CDATA[<p>What I noticed about this whole ordeal is that it all started as a licensing issue.  You also posted about another licensing bug recently:<br />
<a href="http://vmetc.com/2008/01/25/esx-35-4-socket-host-based-license-patch/" rel="nofollow">http://vmetc.com/2008/01/25/esx-35-4-socket-host-based-license-patch/</a></p>
<p>Both of these issues I think underscore a major problem in the PC industry and its the near psychotic need to implement draconian protection schemes.  The pirates have proven what a waste of time such schemes are (you often see popular software on torrent before its available in the store, all pre-cracked and ready to use).  It doesn&#8217;t even seem to slow them down most of the time.  Instead all it does is inconvenience and sometimes severely damage the paying customer!  </p>
<p>VMware&#8217;s comment about &#8220;no licensing backdoor&#8221; shows they are more concerned with protecting their (faulty) licensing scheme then protecting their enterprise customers.  Its even more baffling when you consider the niche this product fills.  It&#8217;s not exactly a mass market piece of software that needs to fend off the causal pirate.  How many organizations would really be running a pirate copy of a 5,000$ piece of software?</p>
<p>I&#8217;m just waiting for the evidential shift to microsoft/adobe style &#8220;activation&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Pottinger</title>
		<link>http://vmetc.com/2008/08/15/things-that-make-you-go-hmmmm-final-thoughts-on-the-esxesxi-35-update-2-bug/comment-page-1/#comment-5330</link>
		<dc:creator>Ben Pottinger</dc:creator>
		<pubDate>Fri, 15 Aug 2008 15:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=584#comment-5330</guid>
		<description>What I noticed about this whole ordeal is that it all started as a licensing issue.  You also posted about another licensing bug recently:
http://vmetc.com/2008/01/25/esx-35-4-socket-host-based-license-patch/

Both of these issues I think underscore a major problem in the PC industry and its the near psychotic need to implement draconian protection schemes.  The pirates have proven what a waste of time such schemes are (you often see popular software on torrent before its available in the store, all pre-cracked and ready to use).  It doesn&#039;t even seem to slow them down most of the time.  Instead all it does is inconvenience and sometimes severely damage the paying customer!  

VMware&#039;s comment about &quot;no licensing backdoor&quot; shows they are more concerned with protecting their (faulty) licensing scheme then protecting their enterprise customers.  Its even more baffling when you consider the niche this product fills.  It&#039;s not exactly a mass market piece of software that needs to fend off the causal pirate.  How many organizations would really be running a pirate copy of a 5,000$ piece of software?

I&#039;m just waiting for the evidential shift to microsoft/adobe style &quot;activation&quot;.</description>
		<content:encoded><![CDATA[<p>What I noticed about this whole ordeal is that it all started as a licensing issue.  You also posted about another licensing bug recently:<br />
<a href="http://vmetc.com/2008/01/25/esx-35-4-socket-host-based-license-patch/" rel="nofollow">http://vmetc.com/2008/01/25/esx-35-4-socket-host-based-license-patch/</a></p>
<p>Both of these issues I think underscore a major problem in the PC industry and its the near psychotic need to implement draconian protection schemes.  The pirates have proven what a waste of time such schemes are (you often see popular software on torrent before its available in the store, all pre-cracked and ready to use).  It doesn&#8217;t even seem to slow them down most of the time.  Instead all it does is inconvenience and sometimes severely damage the paying customer!  </p>
<p>VMware&#8217;s comment about &#8220;no licensing backdoor&#8221; shows they are more concerned with protecting their (faulty) licensing scheme then protecting their enterprise customers.  Its even more baffling when you consider the niche this product fills.  It&#8217;s not exactly a mass market piece of software that needs to fend off the causal pirate.  How many organizations would really be running a pirate copy of a 5,000$ piece of software?</p>
<p>I&#8217;m just waiting for the evidential shift to microsoft/adobe style &#8220;activation&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

