サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
Pixel 9
timtaubert.de
A few weeks ago I listened to Hanno Böck talk about TLS version intolerance at the Berlin AppSec & Crypto Meetup. He explained how with TLS 1.3 just around the corner there again are growing concerns about faulty TLS stacks found in HTTP servers, load balancers, routers, firewalls, and similar software and devices. I decided to dig a little deeper and will use this post to explain version intolera
Please note that this post is about draft-11 of the TLS v1.3 standard. TLS must be fast. Adoption will greatly benefit from speeding up the initial handshake that authenticates and secures the connection. You want to get the protocol out of the way and start delivering data to visitors as soon as possible. This is crucial if we want the web to succeed at deprecating non-secure HTTP. Let’s start by
After you finished reading this one, please also read the follow-up post that covers session resumption changes in TLS 1.3. The probably oldest complaint about TLS is that its handshake is slow and together with the transport encryption has a lot of CPU overhead. This certainly is not true anymore if configured correctly. One of the most important features to improve user experience for visitors a
October 29, 2014 With the web slowly maturing as a platform the demand for cryptography in the browser has risen, especially in a post-Snowden era. Many of us have heard about the upcoming Web Cryptography API but at the time of writing there seem to be no good introductions available. We will take a look at the proposed W3C spec and its current state of implementation. https://github.com/ttaubert
May 3, 2013 You have probably already heard of generators and iterators coming to a browser near you. They have been available in Firefox for a long time and are used extensively all over the Mozilla code base. The V8 team will implement iterators and generators once ES6 has been finalized. This post describes the current implementation in SpiderMonkey and tries to include the current state of the
You probably have all heard of this weird new thing called Electrolysis (a.k.a. e10s). Basically it’s all about running the browser UI and its tabs in separated processes. I recently rewrote a part of Panorama to be e10s-future-proof and thought I should share what I’ve learned so far… (If you don’t know why we’re all doing this, please read: http://blog.mozilla.com/products/2011/07/15/goals-for-m
このページを最初にブックマークしてみませんか?
『timtaubert.de』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く