<?xml version="1.0" encoding="UTF-8" ?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>sasl_oauth at Yahoo! Groups</title>
    <link>http://groups.yahoo.com/group/sasl_oauth/</link>
    <description>SASL OAUTH Draft discussion</description>

    <item>
      <title>(no subject)</title>
      <pubDate>Sat, 06 Oct 2012 14:01:05 GMT</pubDate>
      <dc:creator>safril salle</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/87</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/87</guid>
      <description>* * * * *Sincerely Best regards Safril Salle* * id.linkedin.com/pub/safril-salle/37/a51/518 E-mail: safril.s0@... ... Mobile: &#43;6282125808817 ... *Buy and</description>
    </item>
    <item>
      <title>Re: emty challenge</title>
      <pubDate>Sat, 27 Aug 2011 00:57:26 GMT</pubDate>
      <dc:creator>William J. Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/86</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/86</guid>
      <description>There doesn&#39;t have to be a difference, but there is a final message on the wire to communicate the success or failure.  We did it this way to make the sate</description>
    </item>
    <item>
      <title>Re: emty challenge</title>
      <pubDate>Fri, 26 Aug 2011 22:41:30 GMT</pubDate>
      <dc:creator>yutaka.obuchi</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/85</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/85</guid>
      <description>Hi, Thank you for your comment. I may be missing something. But as I mentioned, in the SASL IMAP spec(http://tools.ietf.org/html/rfc4959) at Chapter4 Example</description>
    </item>
    <item>
      <title>Re: emty challenge</title>
      <pubDate>Fri, 26 Aug 2011 15:53:04 GMT</pubDate>
      <dc:creator>William J. Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/84</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/84</guid>
      <description>Actually it&#39;s sending back and empty response payload along with the success message in 5.1.  Is it a problem?  From the client perspective we figured it was</description>
    </item>
    <item>
      <title>emty challenge</title>
      <pubDate>Fri, 26 Aug 2011 05:54:13 GMT</pubDate>
      <dc:creator>yutaka.obuchi</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/83</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/83</guid>
      <description>Hi all, I am working on SASL OAuth Patch for Nginx mail module. https://github.com/bucchi/OAuthSASLPatchForNginx. And I have just got a question about Example</description>
    </item>
    <item>
      <title>New draft: draft-mills-kitten-sasl-oauth: Tunneled HTTP Authenticati</title>
      <pubDate>Fri, 08 Jul 2011 19:21:33 GMT</pubDate>
      <dc:creator>Bill Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/82</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/82</guid>
      <description>Hi, I&#39;ve posted a new draft. https://tools.ietf.org/html/draft-mills-kitten-sasl-oauth-03 I believe there is one open issue, and that is whether we&#39;re going to</description>
    </item>
    <item>
      <title>Re: Fireeagle OAuth over XMPP</title>
      <pubDate>Wed, 23 Feb 2011 20:48:52 GMT</pubDate>
      <dc:creator>William J. Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/81</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/81</guid>
      <description>Cool stuff.  They are extending the XMPP XML there to carry the OAuth credential/signature. From: chris.messina &lt;chris.messina&#43;yahoo@...&gt; To:</description>
    </item>
    <item>
      <title>Fireeagle OAuth over XMPP</title>
      <pubDate>Wed, 23 Feb 2011 20:12:45 GMT</pubDate>
      <dc:creator>chris.messina</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/80</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/80</guid>
      <description>Was prompted by Joseph Smarr to post this link to this list: http://fireeagle.yahoo.net/developer/documentation/oauth_over_xmpp Curious if you guys were aware</description>
    </item>
    <item>
      <title>Re: New Version Notification for draft-mills-kitten-sasl-oauth-01</title>
      <pubDate>Thu, 17 Feb 2011 01:10:03 GMT</pubDate>
      <dc:creator>Bill Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/79</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/79</guid>
      <description>Better is http://trac.tools.ietf.org/html/draft-mills-kitten-sasl-oauth-01 ... -bill</description>
    </item>
    <item>
      <title>New Version Notification for draft-mills-kitten-sasl-oauth-01</title>
      <pubDate>Thu, 17 Feb 2011 01:06:33 GMT</pubDate>
      <dc:creator>Bill Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/78</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/78</guid>
      <description>http://www.ietf.org/id/draft-mills-kitten-sasl-oauth-01.txt I&#39;d appreciate any feedback. -bill</description>
    </item>
    <item>
      <title>OAuth SASL mechanisn code.</title>
      <pubDate>Thu, 20 Jan 2011 02:49:26 GMT</pubDate>
      <dc:creator>Bill Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/77</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/77</guid>
      <description>Greetings. Now that I&#39;ve finally gotten permission to put my code out into open source I have an implementation of a SASL mechanism in the Cyrus SASL</description>
    </item>
    <item>
      <title>working code with stub.</title>
      <pubDate>Fri, 16 Jul 2010 23:41:32 GMT</pubDate>
      <dc:creator>Bill Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/76</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/76</guid>
      <description>I have a working SASL mechanism with stubbed out authentication.  I&#39;m happy to send a tarball to anyone willing to accept the warts and blemishes (no</description>
    </item>
    <item>
      <title>So much for simple.....</title>
      <pubDate>Mon, 28 Jun 2010 05:12:23 GMT</pubDate>
      <dc:creator>Bill Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/75</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/75</guid>
      <description>I&#39;ve been poking my way through an implementation of a Cyrus SASL mechanism for OAuth.  I&#39;ve come to the conclusion that simple is easy to write the spec for</description>
    </item>
    <item>
      <title>Re: WebFinger vs host-meta</title>
      <pubDate>Sat, 05 Jun 2010 15:33:21 GMT</pubDate>
      <dc:creator>William Mills</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/74</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/74</guid>
      <description>WebFinger certainly solves a significant part of the problem, but there are some who don&#39;t feel it is enough.  What I&#39;m moving toward is that if the client</description>
    </item>
    <item>
      <title>WebFinger vs host-meta</title>
      <pubDate>Sat, 05 Jun 2010 01:36:21 GMT</pubDate>
      <dc:creator>Marius</dc:creator>
      <link>http://groups.yahoo.com/group/sasl_oauth/message/73</link>
      <guid isPermaLink="true">http://groups.yahoo.com/group/sasl_oauth/message/73</guid>
      <description>One of the suggested discovery methods was to use WebFinger on the user entered email address (or username + host). The actual information that needs to be</description>
    </item>

  </channel>
</rss>
<!-- rss1.grp.bf1.yahoo.com uncompressed Sat May 25 03:44:03 PDT 2013 -->
