<?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"
	>
<channel>
	<title>Comments on: Facebook and XSS - a sample in action! :P</title>
	<atom:link href="http://cubist.cs.washington.edu/Security/2008/03/06/facebook-and-xss-a-sample-in-action-p/feed/" rel="self" type="application/rss+xml" />
	<link>http://cubist.cs.washington.edu/Security/2008/03/06/facebook-and-xss-a-sample-in-action-p/</link>
	<description></description>
	<pubDate>Wed, 20 Aug 2008 16:47:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: joyleung</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/06/facebook-and-xss-a-sample-in-action-p/#comment-3621</link>
		<dc:creator>joyleung</dc:creator>
		<pubDate>Tue, 11 Mar 2008 06:43:11 +0000</pubDate>
		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/06/facebook-and-xss-a-sample-in-action-p/#comment-3621</guid>
		<description>It is somewhat frightening how easy it can be to look up working exploits for software on the internet. Especially if it is the first hit on google. Is it right for people to research into weaknesses (like breaking encryption) and post them openly on the internet? I just wonder if the damage done by posting flaws on the internet exceed the damage that would be done if the software company were contacted privately.</description>
		<content:encoded><![CDATA[<p>It is somewhat frightening how easy it can be to look up working exploits for software on the internet. Especially if it is the first hit on google. Is it right for people to research into weaknesses (like breaking encryption) and post them openly on the internet? I just wonder if the damage done by posting flaws on the internet exceed the damage that would be done if the software company were contacted privately.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: felixctc</title>
		<link>http://cubist.cs.washington.edu/Security/2008/03/06/facebook-and-xss-a-sample-in-action-p/#comment-3457</link>
		<dc:creator>felixctc</dc:creator>
		<pubDate>Sat, 08 Mar 2008 21:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/2008/03/06/facebook-and-xss-a-sample-in-action-p/#comment-3457</guid>
		<description>To tie this to what we learned recently from a guest lecture, it also shows how important it is to take security into considerations during the design and implementation stage in a software development lifecycle. This way, attacks like this wouldn't be so easy to execute.

Here's a link that talks a little more about hackers attacks on MySpace and facebook.:
http://www.computing.co.uk/vnunet/news/2210932/buffer-overflow-hacks-target</description>
		<content:encoded><![CDATA[<p>To tie this to what we learned recently from a guest lecture, it also shows how important it is to take security into considerations during the design and implementation stage in a software development lifecycle. This way, attacks like this wouldn&#8217;t be so easy to execute.</p>
<p>Here&#8217;s a link that talks a little more about hackers attacks on MySpace and facebook.:<br />
<a href="http://www.computing.co.uk/vnunet/news/2210932/buffer-overflow-hacks-target" rel="nofollow">http://www.computing.co.uk/vnunet/news/2210932/buffer-overflow-hacks-target</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
