<story><title>Go 1.12 Released</title><url>https://blog.golang.org/go1.12</url></story><parent_chain><item><author>FiloSottile</author><text>_o&amp;#x2F; hello HN, this release ships with seamless opt-in support for TLS 1.3 in crypto&amp;#x2F;tls. (Gated by the GODEBUG=tls13=1 environment variable.)&lt;p&gt;I&amp;#x27;d be happy to answer any questions about it, or about the rest of the Go cryptography libraries!</text></item></parent_chain><comment><author>mholt</author><text>I&amp;#x27;ll add, too, that anyone who wants to try TLS 1.3 right now can do so with the latest source builds of the Caddy web server. We just merged support for TLS 1.3 a few minutes after the Go 1.12 release: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mholt&amp;#x2F;caddy&amp;#x2F;pull&amp;#x2F;2399&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;mholt&amp;#x2F;caddy&amp;#x2F;pull&amp;#x2F;2399&lt;/a&gt;&lt;p&gt;If you have a domain name pointed at your machine:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    $ caddy -host example.com
&lt;/code&gt;&lt;/pre&gt;
(Roughly equivalent to python -m SimpleHTTPServer but with HTTPS, and production-ready.)&lt;p&gt;Or if you just want to try things out:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    $ caddy &amp;quot;tls self_signed&amp;quot;&lt;/code&gt;&lt;/pre&gt;</text></comment>
<story><title>Go 1.12 Released</title><url>https://blog.golang.org/go1.12</url></story><parent_chain><item><author>FiloSottile</author><text>_o&amp;#x2F; hello HN, this release ships with seamless opt-in support for TLS 1.3 in crypto&amp;#x2F;tls. (Gated by the GODEBUG=tls13=1 environment variable.)&lt;p&gt;I&amp;#x27;d be happy to answer any questions about it, or about the rest of the Go cryptography libraries!</text></item></parent_chain><comment><author>crawshaw</author><text>Any concerns exposing Go tls1.3 directly to the internet today?&lt;p&gt;Is 0-RTT on the roadmap for Go 1.13?</text></comment>