<?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: VMware free ESXi 3.5 Update 3 RCLI APIs opened unintentionally</title>
	<atom:link href="http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Tue, 17 Apr 2012 03:50:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: VMware Easter Egg? Easy Install of ESXi 4 On VMware Player 3.0 &#124; VM /ETC</title>
		<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/comment-page-1/#comment-3396</link>
		<dc:creator>VMware Easter Egg? Easy Install of ESXi 4 On VMware Player 3.0 &#124; VM /ETC</dc:creator>
		<pubDate>Sat, 31 Oct 2009 19:40:12 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/#comment-3396</guid>
		<description>[...] left in the new release of VMware Player. Remember when remote administration of ESXi 3.5 was accidentally left enabled? Otherwise, this is the first VMware &#8220;virtual Easter Egg&#8221; that I am aware [...]</description>
		<content:encoded><![CDATA[<p>[...] left in the new release of VMware Player. Remember when remote administration of ESXi 3.5 was accidentally left enabled? Otherwise, this is the first VMware &#8220;virtual Easter Egg&#8221; that I am aware [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Things That Make you Go Hmmmm - VMware Requests Veeam Discontinue Support for Free ESXi in Veeam Backup? &#124; VM /ETC</title>
		<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/comment-page-1/#comment-2582</link>
		<dc:creator>Things That Make you Go Hmmmm - VMware Requests Veeam Discontinue Support for Free ESXi in Veeam Backup? &#124; VM /ETC</dc:creator>
		<pubDate>Thu, 04 Jun 2009 03:13:22 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/#comment-2582</guid>
		<description>[...] ESXi Update 3 is mistakenly released with remote administration left open via the RCLI. VMware recognizes the mistake and closes back down remote administration with ESXi Update 4 [...]</description>
		<content:encoded><![CDATA[<p>[...] ESXi Update 3 is mistakenly released with remote administration left open via the RCLI. VMware recognizes the mistake and closes back down remote administration with ESXi Update 4 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ESXi U4 Ends Free Version Read and Write Access from the RCLI &#124; VM /ETC</title>
		<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/comment-page-1/#comment-2278</link>
		<dc:creator>ESXi U4 Ends Free Version Read and Write Access from the RCLI &#124; VM /ETC</dc:creator>
		<pubDate>Wed, 01 Apr 2009 01:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/#comment-2278</guid>
		<description>[...] read and write access to free ESXi U3 via the RCLI was announced here on VM /ETC and then quickly reported as a mistake that VMware would &#8220;fix&#8221; in an upcoming [...]</description>
		<content:encoded><![CDATA[<p>[...] read and write access to free ESXi U3 via the RCLI was announced here on VM /ETC and then quickly reported as a mistake that VMware would &#8220;fix&#8221; in an upcoming [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ESXi U4 Ends Free Version Read and Write Access from the RCLI &#124; VM /ETC</title>
		<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/comment-page-1/#comment-2279</link>
		<dc:creator>ESXi U4 Ends Free Version Read and Write Access from the RCLI &#124; VM /ETC</dc:creator>
		<pubDate>Wed, 01 Apr 2009 01:10:28 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/#comment-2279</guid>
		<description>[...] read and write access to free ESXi U3 via the RCLI was announced here on VM /ETC and then quickly reported as a mistake that VMware would &#8220;fix&#8221; in an upcoming [...]</description>
		<content:encoded><![CDATA[<p>[...] read and write access to free ESXi U3 via the RCLI was announced here on VM /ETC and then quickly reported as a mistake that VMware would &#8220;fix&#8221; in an upcoming [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hypervisor.fr &#187; Blog Archive &#187; ESXi et le-faux-cadeau-de-Noël-caché</title>
		<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/comment-page-1/#comment-1667</link>
		<dc:creator>Hypervisor.fr &#187; Blog Archive &#187; ESXi et le-faux-cadeau-de-Noël-caché</dc:creator>
		<pubDate>Wed, 17 Dec 2008 18:41:20 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/#comment-1667</guid>
		<description>[...] Mais en fait, non : With the release of VMware ESXi 3.5 Update 3, some API calls became freely available.  As it turns out, these new APIs were opened up unintentionally.  This inadvertent change happened when VMware was resolving an API-related bug. [...]</description>
		<content:encoded><![CDATA[<p>[...] Mais en fait, non : With the release of VMware ESXi 3.5 Update 3, some API calls became freely available.  As it turns out, these new APIs were opened up unintentionally.  This inadvertent change happened when VMware was resolving an API-related bug. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Professional VMware &#187; Blog Archive &#187; ESXi 3.5 Update 3 API&#8217;s Unlocked By Accident</title>
		<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/comment-page-1/#comment-1663</link>
		<dc:creator>Professional VMware &#187; Blog Archive &#187; ESXi 3.5 Update 3 API&#8217;s Unlocked By Accident</dc:creator>
		<pubDate>Wed, 17 Dec 2008 00:50:19 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/#comment-1663</guid>
		<description>[...] out from VM/Etc and a few other sources today, that the recent opening of the ESXi 3.5 Update 3 API’s was an [...]</description>
		<content:encoded><![CDATA[<p>[...] out from VM/Etc and a few other sources today, that the recent opening of the ESXi 3.5 Update 3 API’s was an [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/comment-page-1/#comment-1654</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Tue, 16 Dec 2008 13:52:53 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/#comment-1654</guid>
		<description>This is a bummer. Why are they locked down in the first place, when un-locking makes it easier and quicker to administer??</description>
		<content:encoded><![CDATA[<p>This is a bummer. Why are they locked down in the first place, when un-locking makes it easier and quicker to administer??</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tom</title>
		<link>http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/comment-page-1/#comment-5595</link>
		<dc:creator>tom</dc:creator>
		<pubDate>Tue, 16 Dec 2008 13:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/2008/12/15/vmware-free-esxi-35-update-3-rcli-apis-opened-unintentionally/#comment-5595</guid>
		<description>This is a bummer. Why are they locked down in the first place, when un-locking makes it easier and quicker to administer??</description>
		<content:encoded><![CDATA[<p>This is a bummer. Why are they locked down in the first place, when un-locking makes it easier and quicker to administer??</p>
]]></content:encoded>
	</item>
</channel>
</rss>

