<?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: Security Review: Facebook Applications</title>
	<atom:link href="http://cubist.cs.washington.edu/Security/2009/01/09/security-review-facebook-applications/feed/" rel="self" type="application/rss+xml" />
	<link>http://cubist.cs.washington.edu/Security/2009/01/09/security-review-facebook-applications/</link>
	<description></description>
	<lastBuildDate>Mon, 25 May 2009 11:35:08 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lisa Permatasari</title>
		<link>http://cubist.cs.washington.edu/Security/2009/01/09/security-review-facebook-applications/comment-page-1/#comment-6009</link>
		<dc:creator>Lisa Permatasari</dc:creator>
		<pubDate>Sat, 17 Jan 2009 02:33:34 +0000</pubDate>
		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/?p=397#comment-6009</guid>
		<description>I also agree that Facebook should have rules of who have permission of writing applications. Like stated in the review, developers can have access to the database, so if developers who have bad intention are making applications, they can play around with the database. They can steal users&#039; private information. Or it could be that irresponsible developers misused the database.

One solution that I could think about is for Facebook to choose some applications randomly and check them. By doing this, there is possibility that they find any security problem in the codes and if the application is malicious, they can block the developer from making another application.</description>
		<content:encoded><![CDATA[<p>I also agree that Facebook should have rules of who have permission of writing applications. Like stated in the review, developers can have access to the database, so if developers who have bad intention are making applications, they can play around with the database. They can steal users&#8217; private information. Or it could be that irresponsible developers misused the database.</p>
<p>One solution that I could think about is for Facebook to choose some applications randomly and check them. By doing this, there is possibility that they find any security problem in the codes and if the application is malicious, they can block the developer from making another application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Miller</title>
		<link>http://cubist.cs.washington.edu/Security/2009/01/09/security-review-facebook-applications/comment-page-1/#comment-5984</link>
		<dc:creator>Sean Miller</dc:creator>
		<pubDate>Thu, 15 Jan 2009 20:23:56 +0000</pubDate>
		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/?p=397#comment-5984</guid>
		<description>With social networking sites being as popular as they are, they are certainly going to be targets of not only attacks such as hacking, but also social engineering attacks.  I agree with Kosh that Facebook has definitely jumped the gun on allowing 3rd parties, of whom they seem to have little legal responsibility for, to have access to the entirety of our and our friends profile information.

It seems to me that they could cut down on the likely hood of an attack by allowing only trusted developers to publish content for applications, but it removes the openness of Facebook.

With the amount of information that is stored on Facebook and how easily a faulty application can be used to step around privacy barriers, Facebook should highly consider either spending the money to make these applications safe, or limit what can be published.  Without either of these steps, Facebook looks like a huge threat just waiting to be leapt upon.</description>
		<content:encoded><![CDATA[<p>With social networking sites being as popular as they are, they are certainly going to be targets of not only attacks such as hacking, but also social engineering attacks.  I agree with Kosh that Facebook has definitely jumped the gun on allowing 3rd parties, of whom they seem to have little legal responsibility for, to have access to the entirety of our and our friends profile information.</p>
<p>It seems to me that they could cut down on the likely hood of an attack by allowing only trusted developers to publish content for applications, but it removes the openness of Facebook.</p>
<p>With the amount of information that is stored on Facebook and how easily a faulty application can be used to step around privacy barriers, Facebook should highly consider either spending the money to make these applications safe, or limit what can be published.  Without either of these steps, Facebook looks like a huge threat just waiting to be leapt upon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hanum</title>
		<link>http://cubist.cs.washington.edu/Security/2009/01/09/security-review-facebook-applications/comment-page-1/#comment-5979</link>
		<dc:creator>hanum</dc:creator>
		<pubDate>Tue, 13 Jan 2009 14:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/?p=397#comment-5979</guid>
		<description>So, how to prevent a Facebook hack from suspicious 3rd party applications? Any suggestion? Thank&#039;s before


&lt;a href=&quot;http://gunadarma.ac.id&quot; rel=&quot;nofollow&quot;&gt;&lt;strong&gt;Gunadarma University&lt;/strong&gt;&lt;/a&gt;
Indonesia</description>
		<content:encoded><![CDATA[<p>So, how to prevent a Facebook hack from suspicious 3rd party applications? Any suggestion? Thank&#8217;s before</p>
<p><a href="http://gunadarma.ac.id" rel="nofollow"><strong>Gunadarma University</strong></a><br />
Indonesia</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joylynford</title>
		<link>http://cubist.cs.washington.edu/Security/2009/01/09/security-review-facebook-applications/comment-page-1/#comment-5977</link>
		<dc:creator>Joylynford</dc:creator>
		<pubDate>Tue, 13 Jan 2009 09:33:12 +0000</pubDate>
		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/?p=397#comment-5977</guid>
		<description>the recent reports regarding the hacking of social bookmarking accounts has made me to think twice to be a part of such sites. is facebook protected towards such hacking</description>
		<content:encoded><![CDATA[<p>the recent reports regarding the hacking of social bookmarking accounts has made me to think twice to be a part of such sites. is facebook protected towards such hacking</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kosh</title>
		<link>http://cubist.cs.washington.edu/Security/2009/01/09/security-review-facebook-applications/comment-page-1/#comment-5970</link>
		<dc:creator>kosh</dc:creator>
		<pubDate>Mon, 12 Jan 2009 05:23:53 +0000</pubDate>
		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/?p=397#comment-5970</guid>
		<description>I really think that Facebook jumped the gun released it&#039;s application framework a little too soon. 

For one, there is no way for the company to police all of the apps submitted without incurring huge cost overhead. But, for a company like Facebook, which still doesn&#039;t quite have model to generate money from users, this is definitely a hard thing to do.

The result? --&gt; The users get short changed and are put at risk while facebook tries to experiment apps as a way make money (or break even).

I really don&#039;t see a viable solution for this issue unless it is acquired by a big profit generating corporation (read Google or M$) which has the resources and the a reputation at stake (to guarantee privacy and security for the user).</description>
		<content:encoded><![CDATA[<p>I really think that Facebook jumped the gun released it&#8217;s application framework a little too soon. </p>
<p>For one, there is no way for the company to police all of the apps submitted without incurring huge cost overhead. But, for a company like Facebook, which still doesn&#8217;t quite have model to generate money from users, this is definitely a hard thing to do.</p>
<p>The result? &#8211;&gt; The users get short changed and are put at risk while facebook tries to experiment apps as a way make money (or break even).</p>
<p>I really don&#8217;t see a viable solution for this issue unless it is acquired by a big profit generating corporation (read Google or M$) which has the resources and the a reputation at stake (to guarantee privacy and security for the user).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Facebook Security</title>
		<link>http://cubist.cs.washington.edu/Security/2009/01/09/security-review-facebook-applications/comment-page-1/#comment-5962</link>
		<dc:creator>Facebook Security</dc:creator>
		<pubDate>Sat, 10 Jan 2009 08:03:24 +0000</pubDate>
		<guid isPermaLink="false">http://cubist.cs.washington.edu/Security/?p=397#comment-5962</guid>
		<description>[...] the website of the University of Washington Computer Security and Research, they have posted a review on facebook security, which is worth reading for anyone with an account with that [...]</description>
		<content:encoded><![CDATA[<p>[...] the website of the University of Washington Computer Security and Research, they have posted a review on facebook security, which is worth reading for anyone with an account with that [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
