<?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: Google Friend Connect Site on Joyent Accelerators</title>
	<atom:link href="http://joyeur.com/2008/05/13/friend-connect-site-on-joyent-accelerators/feed/" rel="self" type="application/rss+xml" />
	<link>http://joyeur.com/2008/05/13/friend-connect-site-on-joyent-accelerators/</link>
	<description>Joyent&#039;s Weblog</description>
	<lastBuildDate>Wed, 28 Mar 2012 23:03:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Micheal</title>
		<link>http://joyeur.com/2008/05/13/friend-connect-site-on-joyent-accelerators/#comment-3184</link>
		<dc:creator><![CDATA[Micheal]]></dc:creator>
		<pubDate>Wed, 14 May 2008 05:35:00 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/friend-connect-site-on-joyent-accelerators/#comment-3184</guid>
		<description><![CDATA[Is this opening up a can of security worms?

	I&#8217;ll explain.

	So I went out to the BibleApps site and clicked &#8220;Sign in&#8221;.

	It presented me with signing in with Google/Yahoo/AIM/etc.

	(Immediately, I think &#8211; oh no.  This is going to open up a can of worms by unethical sites faking login pages.)

	The reason being, for years &#8211; we have instructed people for security reason to NEVER give out their login information for site X when on site Y.

	Now OpenID and Friend Connect changes all of that.  Now, it&#8217;s &#8220;okay&#8221; to give out your Google/Yahoo login information when not on a Google/Yahoo site.

	What concerns me is, how do we explain to people now that this is alright?  And how do we prevent unethical people from capturing someones Google/Yahoo login information on a fake-login page and then pass that information onto Google/Yahoo?

	Does that make sense?

	I really like the functionality of Friend Connect and OpenID, and I&#8217;m sure it&#8217;s implemented in a secure way &#8230; what concerns me is that it now seems like it will be extremely easy for sites to &#8220;fake&#8221; a Google/Yahoo login page because we are now training people that it&#8217;s alright to give out your login credentials for a third party site (like BibleApps)]]></description>
		<content:encoded><![CDATA[<p>Is this opening up a can of security worms?</p>
<p>	I&#8217;ll explain.</p>
<p>	So I went out to the BibleApps site and clicked &#8220;Sign in&#8221;.</p>
<p>	It presented me with signing in with Google/Yahoo/AIM/etc.</p>
<p>	(Immediately, I think &#8211; oh no.  This is going to open up a can of worms by unethical sites faking login pages.)</p>
<p>	The reason being, for years &#8211; we have instructed people for security reason to NEVER give out their login information for site X when on site Y.</p>
<p>	Now OpenID and Friend Connect changes all of that.  Now, it&#8217;s &#8220;okay&#8221; to give out your Google/Yahoo login information when not on a Google/Yahoo site.</p>
<p>	What concerns me is, how do we explain to people now that this is alright?  And how do we prevent unethical people from capturing someones Google/Yahoo login information on a fake-login page and then pass that information onto Google/Yahoo?</p>
<p>	Does that make sense?</p>
<p>	I really like the functionality of Friend Connect and OpenID, and I&#8217;m sure it&#8217;s implemented in a secure way &#8230; what concerns me is that it now seems like it will be extremely easy for sites to &#8220;fake&#8221; a Google/Yahoo login page because we are now training people that it&#8217;s alright to give out your login credentials for a third party site (like BibleApps)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

