<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>What The Hell? Security</title>
	<atom:link href="http://whatthehellsecurity.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://whatthehellsecurity.com</link>
	<description>startling new ways of thinking about security</description>
	<lastBuildDate>Wed, 16 Feb 2011 08:38:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='whatthehellsecurity.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>What The Hell? Security</title>
		<link>http://whatthehellsecurity.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://whatthehellsecurity.com/osd.xml" title="What The Hell? Security" />
	<atom:link rel='hub' href='http://whatthehellsecurity.com/?pushpress=hub'/>
		<item>
		<title>When Security is Bad for Security</title>
		<link>http://whatthehellsecurity.com/2010/09/21/when-security-is-bad-for-security/</link>
		<comments>http://whatthehellsecurity.com/2010/09/21/when-security-is-bad-for-security/#comments</comments>
		<pubDate>Tue, 21 Sep 2010 20:32:50 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[fraud]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[security sense]]></category>
		<category><![CDATA[security soapbox]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=2037</guid>
		<description><![CDATA[Copyright © What The Hell? Security There are 3 kinds of security in business:  Good security, acceptable security and bad security. Good security is the kind that works for the business and for the people who work in it.  It aligns with universally known objectives, and is communicated in a way that motivates people to [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=2037&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/09/21/when-security-is-bad-for-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/09/chase-email1.png?w=150" medium="image">
			<media:title type="html">chase-email</media:title>
		</media:content>
	</item>
		<item>
		<title>iPhone Premature Messaging Vulnerability</title>
		<link>http://whatthehellsecurity.com/2010/09/20/iphone-premature-messaging-vulnerability/</link>
		<comments>http://whatthehellsecurity.com/2010/09/20/iphone-premature-messaging-vulnerability/#comments</comments>
		<pubDate>Mon, 20 Sep 2010 21:32:56 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[stupid]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=2016</guid>
		<description><![CDATA[Copyright © What The Hell Security Call me a heathen.  I recently bought my first iPhone. I&#8217;ve owned about 15 too many Dangleberries. After accidentally dropping the last one and watching it land 75 horizontal feet from where I was standing at the time, I gave an HTC Aria running Android a try. One of [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=2016&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/09/20/iphone-premature-messaging-vulnerability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/09/esc-flowchart.png?w=150" medium="image">
			<media:title type="html">esc-flowchart</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/09/dang1.png?w=300" medium="image">
			<media:title type="html">dang</media:title>
		</media:content>
	</item>
		<item>
		<title>FTC to Twitter: &#8220;Do Not Be Concerned About Security&#8221;</title>
		<link>http://whatthehellsecurity.com/2010/07/28/ftc-to-twitter-do-not-be-concerned-about-security/</link>
		<comments>http://whatthehellsecurity.com/2010/07/28/ftc-to-twitter-do-not-be-concerned-about-security/#comments</comments>
		<pubDate>Wed, 28 Jul 2010 07:55:43 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[security humor]]></category>
		<category><![CDATA[security sense]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=1994</guid>
		<description><![CDATA[Copyright © What The Hell? Security [For context see "The FTC's Bitter-Tweet Victory over Twitter"] The Federal Trade Commission today issued a clarifying statement regarding its recently announced ruling that Twitter had not lived up to its promise of years past to protect consumers&#8217; personal information. &#8220;The FTC wishes to reiterate our ruling that Twitter [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=1994&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/07/28/ftc-to-twitter-do-not-be-concerned-about-security/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>
	</item>
		<item>
		<title>The FTC&#8217;s Bitter-Tweet Victory over Twitter</title>
		<link>http://whatthehellsecurity.com/2010/07/26/the-ftcs-bitter-tweet-victory-over-twitter/</link>
		<comments>http://whatthehellsecurity.com/2010/07/26/the-ftcs-bitter-tweet-victory-over-twitter/#comments</comments>
		<pubDate>Mon, 26 Jul 2010 19:17:11 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[security sense]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=1906</guid>
		<description><![CDATA[Copyright © What The Hell? Security Few security happenings leave me speechless. The FTC&#8217;s insanely aggressive settlement over Twitter&#8217;s 2009 privacy gaffes practically yanked my tongue clear out of my mouth. First off, let&#8217;s be honest with ourselves for a minute. This is Twitter we&#8217;re talking about. Twitter isn&#8217;t a bank. It isn&#8217;t a medical institution. [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=1906&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/07/26/the-ftcs-bitter-tweet-victory-over-twitter/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>
	</item>
		<item>
		<title>Symantec, VeriSign Off To Rocky Start</title>
		<link>http://whatthehellsecurity.com/2010/07/15/symantec-verisign-off-to-rocky-start/</link>
		<comments>http://whatthehellsecurity.com/2010/07/15/symantec-verisign-off-to-rocky-start/#comments</comments>
		<pubDate>Thu, 15 Jul 2010 20:18:15 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[certificate authorities]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=1846</guid>
		<description><![CDATA[Copyright © What The Hell? Security I still find Symantec&#8217;s purchase of VeriSign&#8217;s security business intriguing. So I decided to do a little research. All I&#8217;m gonna say is, nothing beats a little dumpster diving. Look past the scribbles and you&#8217;ll find that each company raises some really good points about security-related problems with the other&#8217;s [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=1846&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/07/15/symantec-verisign-off-to-rocky-start/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/07/rocky-start-1.png?w=150" medium="image">
			<media:title type="html">rocky-start-1</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/07/rocky-start-2.png?w=150" medium="image">
			<media:title type="html">rocky-start-2</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/07/rocky-start-3.png?w=150" medium="image">
			<media:title type="html">rocky-start-3</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/07/rocky-start-4.png?w=150" medium="image">
			<media:title type="html">rocky-start-4</media:title>
		</media:content>
	</item>
		<item>
		<title>Security World Cup: Microsoft 171, Google 22</title>
		<link>http://whatthehellsecurity.com/2010/07/05/security-world-cup-microsoft-171-google-22/</link>
		<comments>http://whatthehellsecurity.com/2010/07/05/security-world-cup-microsoft-171-google-22/#comments</comments>
		<pubDate>Mon, 05 Jul 2010 20:49:59 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=1780</guid>
		<description><![CDATA[Copyright © What The Hell? Security Hey Google, what the hell? Not that we&#8217;re keeping score or anything (see graph), but your Online Security Blog&#8216;s quietude relative to Microsoft&#8217;s Trustworthy Computing Security and Privacy Blog is begging for a fan riot. According to my screen-scraping calculus, for the 18 months of January 2009 through June [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=1780&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/07/05/security-world-cup-microsoft-171-google-22/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/07/microsoft-vs-google-security-blogs1.png?w=150" medium="image">
			<media:title type="html">microsoft-vs-google-security-blogs</media:title>
		</media:content>
	</item>
		<item>
		<title>The 9 Laws of Phishing (Part 3)</title>
		<link>http://whatthehellsecurity.com/2010/06/27/the-9-laws-of-phishing-part-3/</link>
		<comments>http://whatthehellsecurity.com/2010/06/27/the-9-laws-of-phishing-part-3/#comments</comments>
		<pubDate>Sun, 27 Jun 2010 10:12:42 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[certificate authorities]]></category>
		<category><![CDATA[hypertext]]></category>
		<category><![CDATA[malware]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[security sense]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=1682</guid>
		<description><![CDATA[Copyright © What The Hell? Security [ Part 1 &#124; Part 2 &#124; Part 3 ] (continued ) The 9 Laws tell us quite a bit about designing a viable platform solution.  Let&#8217;s step through them again, sketching as we go. Law 1:  Phishing Is About Commerce Web 1.0 was all about commerce.  Only we [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=1682&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/06/27/the-9-laws-of-phishing-part-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>
	</item>
		<item>
		<title>VeriSign Says “What The Hell? Security” Blogger Was Right</title>
		<link>http://whatthehellsecurity.com/2010/06/08/verisign-says-what-the-hell-security-blogger-was-right/</link>
		<comments>http://whatthehellsecurity.com/2010/06/08/verisign-says-what-the-hell-security-blogger-was-right/#comments</comments>
		<pubDate>Tue, 08 Jun 2010 07:13:12 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[certificate authorities]]></category>
		<category><![CDATA[fraud]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[ssl]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=1723</guid>
		<description><![CDATA[Copyright © What The Hell? Security MOUNTING VIEW, June 7, 2010 &#8212; VeriSign today acknowledged that the real reason it sold its Authentication Services business to Symantec is that it felt remorse over its SSL bribing business model after reading a post at What The Hell? Security. &#8220;Once that What The Hell? Security guy exposed us, we knew [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=1723&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/06/08/verisign-says-what-the-hell-security-blogger-was-right/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/06/dollar-sign-logo.png?w=300" medium="image">
			<media:title type="html">dollar-sign-logo</media:title>
		</media:content>
	</item>
		<item>
		<title>Phishing: Full or Responsible Disclosure?</title>
		<link>http://whatthehellsecurity.com/2010/05/16/phishing-full-or-responsible-disclosure/</link>
		<comments>http://whatthehellsecurity.com/2010/05/16/phishing-full-or-responsible-disclosure/#comments</comments>
		<pubDate>Mon, 17 May 2010 06:20:16 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[fraud]]></category>
		<category><![CDATA[phishing]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=1628</guid>
		<description><![CDATA[Copyright © What The Hell? Security I&#8217;m on the horns of a dilemma. I&#8217;ve come up with a few phishing use cases not yet witnessed in the wild. Should I exercise full disclosure or responsible disclosure? That&#8217;s a completely nonsensical question of course. Who the hell would I report it to? Onguard Online? Phishtank? APWG?&#160; [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=1628&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/05/16/phishing-full-or-responsible-disclosure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/06/disclosure.png?w=147" medium="image">
			<media:title type="html">disclosure</media:title>
		</media:content>
	</item>
		<item>
		<title>Introducing the Official What The Hell? Security Glossary</title>
		<link>http://whatthehellsecurity.com/2010/05/03/introducing-the-official-what-the-hell-security-glossary/</link>
		<comments>http://whatthehellsecurity.com/2010/05/03/introducing-the-official-what-the-hell-security-glossary/#comments</comments>
		<pubDate>Mon, 03 May 2010 19:17:53 +0000</pubDate>
		<dc:creator>hell if i know</dc:creator>
				<category><![CDATA[certificate authorities]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://whatthehellsecurity.com/?p=1674</guid>
		<description><![CDATA[Do you know that browsers do not implement blacklists?&#160; (Hint: They&#8217;re blocklists.) And that&#160;bribing your Certificate Authority is perfectly legal? Or that you must license the right to render your website&#8217;s URLs &#160;with a background color of&#160; green in browser address bars? And what the hell exactly are the Certificate Warnings from Hell? And the [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=whatthehellsecurity.com&amp;blog=8356378&amp;post=1674&amp;subd=whatthehellsecurity&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://whatthehellsecurity.com/2010/05/03/introducing-the-official-what-the-hell-security-glossary/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="" medium="image">
			<media:title type="html">ljh</media:title>
		</media:content>

		<media:content url="http://whatthehellsecurity.files.wordpress.com/2010/05/whatthehellipedia.png?w=300" medium="image">
			<media:title type="html">whatthehellipedia</media:title>
		</media:content>
	</item>
	</channel>
</rss>
