<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Another Blogger - Latest Comments in Don&amp;#8217;t Make Your Blog an OpenID Provider</title><link>http://anotherblogger.disqus.com/</link><description></description><atom:link href="https://anotherblogger.disqus.com/don8217t_make_your_blog_an_openid_provider/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 04 Dec 2008 23:50:12 -0000</lastBuildDate><item><title>Re: Don&amp;#8217;t Make Your Blog an OpenID Provider</title><link>http://www.anotherblogger.com/2008/10/06/dont-make-your-blog-an-openid-provider/#comment-16036514</link><description>&lt;p&gt;That's a good point Al... if one has weak security on their blog, someone could potentially hijack that redirect and point it to another OpenID provider.  Just another factor for consideration.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ahockley</dc:creator><pubDate>Thu, 04 Dec 2008 23:50:12 -0000</pubDate></item><item><title>Re: Don&amp;#8217;t Make Your Blog an OpenID Provider</title><link>http://www.anotherblogger.com/2008/10/06/dont-make-your-blog-an-openid-provider/#comment-16036513</link><description>&lt;p&gt;A good post to make people consider if they really want to entrust their identity to the security of their blog - made me reconsider my plans.&lt;/p&gt;&lt;p&gt;Do you perhaps end it by contradicting yourself - if I enable openId delegation on my personal blog - surely the same security consdierations come into play - does it matter if I use verisign if someone can hack into my blog and redirect to another openId provider to validate me?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Al Briggs</dc:creator><pubDate>Thu, 04 Dec 2008 04:41:21 -0000</pubDate></item><item><title>Re: Don&amp;#8217;t Make Your Blog an OpenID Provider</title><link>http://www.anotherblogger.com/2008/10/06/dont-make-your-blog-an-openid-provider/#comment-16036512</link><description>&lt;p&gt;But wait, I was about to go to OpenID for everything!  Actually no, all my secure stuff is staying with the original, slightly more seriously secure, security apparatusii.  :)&lt;/p&gt;&lt;p&gt;But I look forward to locking down my OpenID stuff even better over the next few weeks and enabling my ID to work with more and more of my sites, sites I use, and other such.&lt;/p&gt;&lt;p&gt;Especially since, I always want your feedback on my articles and you won't use stuff that doesn't use Open ID!  :o  argh!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Adron Hall</dc:creator><pubDate>Sun, 19 Oct 2008 22:42:14 -0000</pubDate></item><item><title>Re: Don&amp;#8217;t Make Your Blog an OpenID Provider</title><link>http://www.anotherblogger.com/2008/10/06/dont-make-your-blog-an-openid-provider/#comment-16036511</link><description>&lt;p&gt;Aaron, I couldn't agree more.  I strongly believe it is important for an individual to have the ability to run their own OpenID provider, if they so choose.  Having near zero barrier to entry is one of the things that makes OpenID great.  That being said, I think some of the OpenID providers that are available today (especially the three you mentioned, along with some of the newer ones using Yubikey) have much better security than WordPress currently does.  I could certainly put all my money under my mattress and rest assured that I have complete control over it, but for now I find putting it in a bank a better option.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">willnorris</dc:creator><pubDate>Tue, 07 Oct 2008 23:04:50 -0000</pubDate></item></channel></rss>