<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Patchlog - Latest Comments in TLS for HTTP</title><link>http://patchlog.disqus.com/</link><description></description><atom:link href="https://patchlog.disqus.com/tls_for_http/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Fri, 19 Jan 2007 06:07:32 -0000</lastBuildDate><item><title>Re: TLS for HTTP</title><link>http://patchlog.com/security/tls-for-http/#comment-2803622</link><description>&lt;p&gt;Firefox 2 has lready support RFC 3546. Check here,&lt;/p&gt;&lt;p&gt;&lt;a href="http://developer.mozilla.org/en/docs/Security_in_Firefox_2" rel="nofollow noopener" target="_blank" title="http://developer.mozilla.org/en/docs/Security_in_Firefox_2"&gt;http://developer.mozilla.or...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;mozilla people planed TLS NSI support . After knowing IE7 would support this, they accelerated they development and implemented in NSS v3.11 (initially they planed this support in NSS v3,12). Check here,&lt;/p&gt;&lt;p&gt;&lt;a href="http://wiki.mozilla.org/NSS:Roadmap" rel="nofollow noopener" target="_blank" title="http://wiki.mozilla.org/NSS:Roadmap"&gt;http://wiki.mozilla.org/NSS...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;They plan to support RFC 2817 with firefox v3.&lt;/p&gt;&lt;p&gt;On the server side, apache v2.2 has built-in support for RFC 2817. The third-party module, mod_gnutls, adds RFC 3546 support to both apache v2.0 and apache v2.2. Check here,&lt;/p&gt;&lt;p&gt;&lt;a href="http://www.outoforder.cc/projects/apache/mod_gnutls/" rel="nofollow noopener" target="_blank" title="http://www.outoforder.cc/projects/apache/mod_gnutls/"&gt;http://www.outoforder.cc/pr...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kill Bill</dc:creator><pubDate>Fri, 19 Jan 2007 06:07:32 -0000</pubDate></item><item><title>Re: TLS for HTTP</title><link>http://patchlog.com/security/tls-for-http/#comment-2803621</link><description>&lt;p&gt;Firefox 2 has lready support RFC 3546. Check here,&lt;/p&gt;&lt;p&gt;    &lt;a href="http://developer.mozilla.org/en/docs/Security_in_Firefox_2" rel="nofollow noopener" target="_blank" title="http://developer.mozilla.org/en/docs/Security_in_Firefox_2"&gt;http://developer.mozilla.or...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;mozilla people planed TLS NSI support . After knowing IE7 would support this, they accelerated they development and implemented in NSS v3.11 (initially they planed this support in NSS v3,12). Check here,&lt;/p&gt;&lt;p&gt;    &lt;a href="http://wiki.mozilla.org/NSS:Roadmap" rel="nofollow noopener" target="_blank" title="http://wiki.mozilla.org/NSS:Roadmap"&gt;http://wiki.mozilla.org/NSS...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;They plan to support RFC 2817 with firefox v3.&lt;/p&gt;&lt;p&gt;You are right about apache 2.2 support both RFCs though.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kill Bill</dc:creator><pubDate>Fri, 19 Jan 2007 05:55:32 -0000</pubDate></item><item><title>Re: TLS for HTTP</title><link>http://patchlog.com/security/tls-for-http/#comment-2803620</link><description>&lt;p&gt;Firefox 2 has lready support RFC 3546. Check here,&lt;/p&gt;&lt;p&gt;&lt;a href="http://developer.mozilla.org/en/docs/Security_in_Firefox_2" rel="nofollow noopener" target="_blank" title="http://developer.mozilla.org/en/docs/Security_in_Firefox_2"&gt;http://developer.mozilla.or...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;mozilla people planed TLS NSI support . After knowing IE7 would support this, they accelerated they development and implemented in NSS v3.11 (initially they planed this support in NSS v3,12). Check here,&lt;/p&gt;&lt;p&gt;&lt;a href="http://wiki.mozilla.org/NSS:Roadmap" rel="nofollow noopener" target="_blank" title="http://wiki.mozilla.org/NSS:Roadmap"&gt;http://wiki.mozilla.org/NSS...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;They plan to support RFC 2817 with firefox v3.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kill Bill</dc:creator><pubDate>Fri, 19 Jan 2007 05:41:46 -0000</pubDate></item></channel></rss>