<?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>Shellshock bug Archives - ESX Virtualization</title>
	<atom:link href="https://www.vladan.fr/tag/shellshock-bug/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.vladan.fr/tag/shellshock-bug/</link>
	<description>VMware ESXi, vSphere, VMware Backup, Hyper-V... how-to, videos....</description>
	<lastBuildDate>Tue, 17 Mar 2015 12:04:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Shellshock (aka Bashdoor) Bug and VMware &#8211; Where are We?</title>
		<link>https://www.vladan.fr/shellshock-aka-bashdoor-bug-vmware/</link>
		
		<dc:creator><![CDATA[Vladan SEGET]]></dc:creator>
		<pubDate>Sun, 05 Oct 2014 11:04:40 +0000</pubDate>
				<category><![CDATA[Free Stuff]]></category>
		<category><![CDATA[Shellshock]]></category>
		<category><![CDATA[Shellshock bug]]></category>
		<guid isPermaLink="false">http://www.vladan.fr/?p=36919</guid>

					<description><![CDATA[<p>Recent Shellshock bug in Linux Bash revealed the 24th of September was often compared to Heartbleed bug in terms of severity. Just to remind you, it affects all Linux/Unix systems using the original bash (which has been re-released for new distros already). OSX users were told to deactivate the advanced Unix services, but apparently even [&#8230;]</p>
<p>Read the full post <a href="https://www.vladan.fr/shellshock-aka-bashdoor-bug-vmware/">Shellshock (aka Bashdoor) Bug and VMware &#8211; Where are We?</a> at <a href="https://www.vladan.fr">ESX Virtualization</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
