<?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: Huge PIN number exposure on website</title>
	<atom:link href="http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/feed/" rel="self" type="application/rss+xml" />
	<link>http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/</link>
	<description>Commentary on the State of Information Security</description>
	<lastBuildDate>Thu, 02 Feb 2012 20:22:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Lori MacVittie</title>
		<link>http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/comment-page-1/#comment-21529</link>
		<dc:creator>Lori MacVittie</dc:creator>
		<pubDate>Fri, 25 Jan 2008 15:24:23 +0000</pubDate>
		<guid isPermaLink="false">http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/#comment-21529</guid>
		<description>LOL. Great post, Vet. 

Must be time to create a regex to filter out those pesky PIN numbers from appearing on web sites and compromising us all.</description>
		<content:encoded><![CDATA[<p>LOL. Great post, Vet. </p>
<p>Must be time to create a regex to filter out those pesky PIN numbers from appearing on web sites and compromising us all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/comment-page-1/#comment-21528</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Fri, 25 Jan 2008 14:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/#comment-21528</guid>
		<description>You had me for about 10 seconds before the coffee started kicking in.  

Martin</description>
		<content:encoded><![CDATA[<p>You had me for about 10 seconds before the coffee started kicking in.  </p>
<p>Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Willingham</title>
		<link>http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/comment-page-1/#comment-21527</link>
		<dc:creator>Andy Willingham</dc:creator>
		<pubDate>Fri, 25 Jan 2008 12:57:29 +0000</pubDate>
		<guid isPermaLink="false">http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/#comment-21527</guid>
		<description>All of my PINS are there! What am I going to do. I can&#039;t think of new numbers for these things. I ruined!!!!!!!!!!</description>
		<content:encoded><![CDATA[<p>All of my PINS are there! What am I going to do. I can&#8217;t think of new numbers for these things. I ruined!!!!!!!!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joat</title>
		<link>http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/comment-page-1/#comment-21526</link>
		<dc:creator>joat</dc:creator>
		<pubDate>Fri, 25 Jan 2008 12:34:30 +0000</pubDate>
		<guid isPermaLink="false">http://infosecplace.com/blog/2008/01/24/huge-pin-number-exposure-on-website/#comment-21526</guid>
		<description>Mike, it&#039;s not 4/1/08 yet!</description>
		<content:encoded><![CDATA[<p>Mike, it&#8217;s not 4/1/08 yet!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

