Every lock needs a key. The hard part is not always designing the lock. Sometimes it is getting the key to the person who needs it. That is the problem I look at in the third post in my CDT series on Encrypted Client Hello. cdt.org/insights/dis...
Post
cdt.orgDistributing the Keys for Private Access to the WebBreaking the DNS Dependencych-22" class="toc-anchor">ECH’s Catch-22thing-strange-in-the-dns" href="#something-strange-in-the-dns" class="toc-anchor">Something Strange in the DNS use it. That’s the fun...
Well-known endpoints, cached configurations, CDN distribution, key transparency mechanisms, and signed ECH configurations are all part of that design space. This is not a reason to give up on ECH. It is a reason to make ECH more deployable under pressure.
0 reposts0 likes
The next step is not just deploying ECH. It is making sure ECH can actually start. cdt.org/insights/dis...
cdt.orgDistributing the Keys for Private Access to the WebBreaking the DNS Dependencych-22" class="toc-anchor">ECH’s Catch-22thing-strange-in-the-dns" href="#something-strange-in-the-dns" class="toc-anchor">Something Strange in the DNS use it. That’s the fun...