TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Changes Coming to TLS: Part Two

59 pointsby remxabout 8 years ago

7 comments

FiloSottileabout 8 years ago
If you prefer the video format, Nick and I gave a talk at 33c3 about how TLS 1.3 works and our experience deploying it at Cloudflare.<p><a href="https:&#x2F;&#x2F;media.ccc.de&#x2F;v&#x2F;33c3-8348-deploying_tls_1_3_the_great_the_good_and_the_bad" rel="nofollow">https:&#x2F;&#x2F;media.ccc.de&#x2F;v&#x2F;33c3-8348-deploying_tls_1_3_the_great...</a>
评论 #14069875 未加载
okketabout 8 years ago
Alternative title: &quot;Sanity Coming to TLS&quot;
评论 #14068811 未加载
vbtechguyabout 8 years ago
Looking forward to TLS 1.3. Starting testing Nginx 1.11.13 + OpenSSL 1.1.0 draft 18 branch with TLS 1.3 myself <a href="https:&#x2F;&#x2F;community.centminmod.com&#x2F;posts&#x2F;47692&#x2F;" rel="nofollow">https:&#x2F;&#x2F;community.centminmod.com&#x2F;posts&#x2F;47692&#x2F;</a> not quite there yet. Needs some love on Nginx end too :)
zedredabout 8 years ago
&gt; If negotiating TLS 1.2, TLS 1.3 servers MUST set the last eight bytes of their Random value to the bytes: 44 4F 57 4E 47 52 44 01<p>If it is possible to do this safely, does that mean the TLS 1.2 Random value was always eight bytes too long? Or that it was unnecessary?
评论 #14070184 未加载
hdhzyabout 8 years ago
Most of these changes seem to just disallow weak cipher suites and RTT-1&#x2F;0 connections.<p>Are there any other differences between modern TLS 1.2 setup and TLS 1.3?
评论 #14069492 未加载
teddyhabout 8 years ago
As I understand it, they are also removing raw public keys and OpenPGP keys, keeping only X.509 certificates.
评论 #14085391 未加载
评论 #14071383 未加载
评论 #14071229 未加载
snakeanusabout 8 years ago
Is there any reason not to use IPSec instead of TLS?
评论 #14070142 未加载