<?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>Darknet - The Darkside &#187; facebook breach</title>
	<atom:link href="http://www.darknet.org.uk/tag/facebook-breach/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.darknet.org.uk</link>
	<description>Ethical Hacking, Penetration Testing &#38; Computer Security</description>
	<lastBuildDate>Thu, 18 Mar 2010 08:50:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Facebook Bug Leaks Birthday Data</title>
		<link>http://www.darknet.org.uk/2008/07/facebook-bug-leaks-birthday-data/</link>
		<comments>http://www.darknet.org.uk/2008/07/facebook-bug-leaks-birthday-data/#comments</comments>
		<pubDate>Thu, 17 Jul 2008 11:10:20 +0000</pubDate>
		<dc:creator>Darknet</dc:creator>
				<category><![CDATA[General Hacking]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[facebook breach]]></category>
		<category><![CDATA[facebook leak]]></category>
		<category><![CDATA[facebook security]]></category>
		<category><![CDATA[facebook testing]]></category>
		<category><![CDATA[facebook-privacy]]></category>
		<category><![CDATA[web privacy]]></category>
		<category><![CDATA[web-application-security]]></category>

		<guid isPermaLink="false">http://www.darknet.org.uk/?p=899</guid>
		<description><![CDATA[It&#8217;s not a big deal but it does show a problem with the way Facebook deals with data and how much power they have over people&#8217;s privacy.
A small slip in coding could cause much worse problems that this, plus this could have happened before but no one picked up on it. It takes a certain [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s not a big deal but it does show a problem with the way Facebook deals with data and how much power they have over people&#8217;s privacy.</p>
<p>A small slip in coding could cause much worse problems that this, plus this could have happened before but no one picked up on it. It takes a certain amount of observational skills to notice something fairly subtle like this.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-3033787195489589";
google_alternate_ad_url = "http://www.darknet.org.uk/google_adsense_script.html";
google_ad_width = 468;
google_ad_height = 60;
google_ad_format = "468x60_as";
google_ad_type = "text";
google_ad_channel ="9647861209";
google_color_border = "FFFFFF";
google_color_bg = "FFFFFF";
google_color_link = "df6f0b";
google_color_url = "df6f0b";
google_color_text = "000000";
//--></script>
<script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<blockquote><p>A glitch in a test version of Facebook&#8217;s Web site inadvertently exposed the birthdays of Facebook&#8217;s 80 million members this week.</p>
<p>The bug was discovered over the weekend by Graham Cluley, a senior technology consultant at Sophos. While checking out Facebook&#8217;s new design, Cluley noticed that the birth dates of some of his privacy-obsessed acquaintances were popping up when they should have been hidden.</p>
<p>Facebook allows users to control who sees private information such as their birth date, which can be a valuable nugget of data for identity thieves. But Cluley discovered that the new site was making this information public to other members. &#8220;Their new profile page essentially ignored the privacy setting to withhold the data of birth,&#8221; he said. </p></blockquote>
<p>As said, identity thieves can have a field day with the birth date, but on Facebook it&#8217;s not too much of a threat.</p>
<p>But as always you shouldn&#8217;t really put anything on ANY website that you don&#8217;t want other people to know about. It could get hacked, sold or like this inadvertently exposed.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-3033787195489589";
google_alternate_ad_url = "http://www.darknet.org.uk/google_adsense_script.html";
google_ad_width = 468;
google_ad_height = 60;
google_ad_format = "468x60_as";
google_ad_type = "text";
google_ad_channel ="9647861209";
google_color_border = "FFFFFF";
google_color_bg = "FFFFFF";
google_color_link = "df6f0b";
google_color_url = "df6f0b";
google_color_text = "000000";
//--></script>
<script type="text/javascript"
  src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
<blockquote><p> &#8220;For a brief period of time, a small number of users were able to access a private beta of Facebook&#8217;s new site design meant only for developers. During that time, some of those users had their birthdays revealed due to a bug,&#8221; Facebook said Wednesday in a statement. The company could not say exactly how long this data was exposed or how many people viewed the beta site, but the bug was patched within hours of Cluley&#8217;s discovery.</p>
<p>Facebook may intend for the beta site to be private, but it has been open to the general public for several days. It features a new profile design that should be rolled out as an option to Facebook users some time this week. </p></blockquote>
<p>Seems like a slip up somewhere with the development workflow, the beta site exposed to the public? The beta tree got merged with the live tree somewhere and rolled out?</p>
<p>I&#8217;m not exactly sure how the Facebook architecture works but I&#8217;d imagine it&#8217;s fairly complex.</p>
<p>Source: <a href="http://www.computerworld.com/action/article.do?command=viewArticleBasic&#038;articleId=9110241&#038;source=rss_news50">ComputerWorld</a></p>
<p align="left"><a class="tt" href="http://twitter.com/home/?status=Facebook+Bug+Leaks+Birthday+Data+http://bit.ly/3EFQLO+from+@THEdarknet" title="Post to Twitter"><img class="nothumb" src="http://www.darknet.org.uk/wp-content/plugins/tweet-this/icons/tt-twitter-micro3.png" alt="Post to Twitter" /></a> <a class="tt" href="http://delicious.com/post?url=http://www.darknet.org.uk/2008/07/facebook-bug-leaks-birthday-data/&amp;title=Facebook+Bug+Leaks+Birthday+Data" title="Post to Delicious"><img class="nothumb" src="http://www.darknet.org.uk/wp-content/plugins/tweet-this/icons/tt-delicious-micro3.png" alt="Post to Delicious" /></a> <a class="tt" href="http://digg.com/submit?url=http://www.darknet.org.uk/2008/07/facebook-bug-leaks-birthday-data/&amp;title=Facebook+Bug+Leaks+Birthday+Data" title="Post to Digg"><img class="nothumb" src="http://www.darknet.org.uk/wp-content/plugins/tweet-this/icons/tt-digg-micro3.png" alt="Post to Digg" /></a> <a class="tt" href="http://www.facebook.com/share.php?u=http://www.darknet.org.uk/2008/07/facebook-bug-leaks-birthday-data/&amp;t=Facebook+Bug+Leaks+Birthday+Data" title="Post to Facebook"><img class="nothumb" src="http://www.darknet.org.uk/wp-content/plugins/tweet-this/icons/tt-facebook-micro3.png" alt="Post to Facebook" /></a> <a class="tt" href="http://stumbleupon.com/submit?url=http://www.darknet.org.uk/2008/07/facebook-bug-leaks-birthday-data/&amp;title=Facebook+Bug+Leaks+Birthday+Data" title="Post to StumbleUpon"><img class="nothumb" src="http://www.darknet.org.uk/wp-content/plugins/tweet-this/icons/tt-su-micro3.png" alt="Post to StumbleUpon" /></a></p>]]></content:encoded>
			<wfw:commentRss>http://www.darknet.org.uk/2008/07/facebook-bug-leaks-birthday-data/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>
