<?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: We’ve been hacked</title>
	<atom:link href="http://www.zendesk.com/blog/weve-been-hacked/feed" rel="self" type="application/rss+xml" />
	<link>http://www.zendesk.com/blog/weve-been-hacked</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Mon, 13 May 2013 09:15:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Tanya Smith</title>
		<link>http://www.zendesk.com/blog/weve-been-hacked#comment-32843</link>
		<dc:creator>Tanya Smith</dc:creator>
		<pubDate>Fri, 22 Feb 2013 02:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zendesk.com/?p=30098#comment-32843</guid>
		<description><![CDATA[Thanks guys, for letting us know. This is happening to every great company I know. It&#039;s really sad these guys aren&#039;t using their talents for service.]]></description>
		<content:encoded><![CDATA[<p>Thanks guys, for letting us know. This is happening to every great company I know. It&#8217;s really sad these guys aren&#8217;t using their talents for service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Mazid</title>
		<link>http://www.zendesk.com/blog/weve-been-hacked#comment-32842</link>
		<dc:creator>Tim Mazid</dc:creator>
		<pubDate>Fri, 22 Feb 2013 02:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zendesk.com/?p=30098#comment-32842</guid>
		<description><![CDATA[To help the rest of us out that may also be affected: what was the vulnerability and the patch for it?  Obviously, if it had to do with internal ZenDesk stuff, there is no need for details; but if it had to do with a common component, a patch would be greatly appreciated.]]></description>
		<content:encoded><![CDATA[<p>To help the rest of us out that may also be affected: what was the vulnerability and the patch for it?  Obviously, if it had to do with internal ZenDesk stuff, there is no need for details; but if it had to do with a common component, a patch would be greatly appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kasper Tidemann</title>
		<link>http://www.zendesk.com/blog/weve-been-hacked#comment-32841</link>
		<dc:creator>Kasper Tidemann</dc:creator>
		<pubDate>Fri, 22 Feb 2013 02:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zendesk.com/?p=30098#comment-32841</guid>
		<description><![CDATA[Thumbs up for being open about what&#039;s happened, most companies wouldn&#039;t be. Even in tough times, you bring the zen. I hope you get it sorted out as quickly as possible.]]></description>
		<content:encoded><![CDATA[<p>Thumbs up for being open about what&#8217;s happened, most companies wouldn&#8217;t be. Even in tough times, you bring the zen. I hope you get it sorted out as quickly as possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Mazid</title>
		<link>http://www.zendesk.com/blog/weve-been-hacked#comment-32840</link>
		<dc:creator>Tim Mazid</dc:creator>
		<pubDate>Fri, 22 Feb 2013 01:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.zendesk.com/?p=30098#comment-32840</guid>
		<description><![CDATA[What was the vulnerability and the patch for it?]]></description>
		<content:encoded><![CDATA[<p>What was the vulnerability and the patch for it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
