<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0">
  <channel>
    <title>Dare Obasanjo aka Carnage4Life - Comments on Does OAuth Have a Dark Side?</title>
    <link>http://www.25hoursaday.com/weblog/</link>
    <description />
    <copyright>Dare Obasanjo</copyright>
    <lastBuildDate>Sat, 07 Nov 2009 17:09:59 GMT</lastBuildDate>
    <generator>newtelligence dasBlog 2.1.8102.813</generator>
    <managingEditor>kpako@yahoo.com</managingEditor>
    <webMaster>kpako@yahoo.com</webMaster>
    <item>
      <author>suppressed@unknown.org (Simon Jones)</author>
      <title>Comment by Simon Jones on "Does OAuth Have a Dark Side?"</title>
      <guid isPermaLink="false">5ecc5753-5269-4df1-9bee-0647cc715453</guid>
      <link>http://www.25hoursaday.com/weblog/CommentView.aspx?guid=397DAAAA-F589-451A-A3D1-53B10975572A</link>
      <pubDate>Sat, 07 Nov 2009 17:09:59 GMT</pubDate>
      <description>Some third party Twitter applications use Twitter for authentication.  If an attacker has a victim's Twitter password, then the attacker can login to one of these applications and stay logged in to the application after the victim changes his Twitter password.  In this scenario, it is useful to offer the user the option to revoke OAuth access tokens.
&lt;br /&gt;&lt;br /&gt;Posted by: Simon Jones</description>
      <comments>http://www.25hoursaday.com/weblog/CommentView.aspx?guid=397DAAAA-F589-451A-A3D1-53B10975572A</comments>
    </item>
  </channel>
</rss>