<?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/"
	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>Comments on: Yet Another Identity Stealing Bug. Will Creeping Normalcy be the Result?</title>
	<atom:link href="http://33bits.org/2010/06/01/yet-another-identity-stealing-bug-will-creeping-normalcy-be-the-result/feed/" rel="self" type="application/rss+xml" />
	<link>http://33bits.org/2010/06/01/yet-another-identity-stealing-bug-will-creeping-normalcy-be-the-result/</link>
	<description>The End of Anonymized Data and What to Do About It</description>
	<lastBuildDate>Thu, 26 Apr 2012 19:07:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Facebook’s Instant Personalization: An Analysis of Fundamental Privacy Flaws &#171; 33 Bits of Entropy</title>
		<link>http://33bits.org/2010/06/01/yet-another-identity-stealing-bug-will-creeping-normalcy-be-the-result/#comment-1670</link>
		<dc:creator><![CDATA[Facebook’s Instant Personalization: An Analysis of Fundamental Privacy Flaws &#171; 33 Bits of Entropy]]></dc:creator>
		<pubDate>Tue, 28 Sep 2010 15:22:24 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=490#comment-1670</guid>
		<description><![CDATA[[...] of leaking your identity to other parties. In my ubercookies series, I documented a series of bugs that can be exploited by an arbitrary website to learn the visitor&#8217;s identity. All of these [...]]]></description>
		<content:encoded><![CDATA[<p>[...] of leaking your identity to other parties. In my ubercookies series, I documented a series of bugs that can be exploited by an arbitrary website to learn the visitor&#8217;s identity. All of these [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: web security trends 2010 &#124; From Information to Intelligence</title>
		<link>http://33bits.org/2010/06/01/yet-another-identity-stealing-bug-will-creeping-normalcy-be-the-result/#comment-1465</link>
		<dc:creator><![CDATA[web security trends 2010 &#124; From Information to Intelligence]]></dc:creator>
		<pubDate>Sun, 06 Jun 2010 19:14:07 +0000</pubDate>
		<guid isPermaLink="false">http://33bits.org/?p=490#comment-1465</guid>
		<description><![CDATA[[...] I won&#8217;t discuss to much this figure as it is already done in this paper.  For me the two important  point regarding  the evolution of web security showed by this figure is that nowadays web security is even more difficult than before. Back in 2005, web security was only about testing few vectors of attacks, mainly XSS and SQL injection. In 2010, the situation is way more complex, as the number of attack vectors exploded. For instance how many of you heard of the new attack released in May named  &#8220;Cross Site URL Hijacking&#8220;  ? In a nutshell this attack allows an attacker to know the URL parameters of a different origin by abusing the Firefox error object. While this attack might seems innocuous, it has serious privacy implications. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] I won&#8217;t discuss to much this figure as it is already done in this paper.  For me the two important  point regarding  the evolution of web security showed by this figure is that nowadays web security is even more difficult than before. Back in 2005, web security was only about testing few vectors of attacks, mainly XSS and SQL injection. In 2010, the situation is way more complex, as the number of attack vectors exploded. For instance how many of you heard of the new attack released in May named  &#8220;Cross Site URL Hijacking&#8220;  ? In a nutshell this attack allows an attacker to know the URL parameters of a different origin by abusing the Firefox error object. While this attack might seems innocuous, it has serious privacy implications. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

