Before the third handshake, server Alice has to require a session renegotiation, including client authentication, on its connection with Mallory, possibly in response to Mallory’s request for some restricted resource. [...]
21.1.2 The timing signal You may be wondering where the timing signal originates from in the encryption process illustrated in Figure 21.1. That source, it turns out, is the HMAC [...]
21.5.1 Lossless compression algorithms In a lossless compression algorithm, the input data is encoded in such a way that its length is decreased. After decoding, however, all of the input [...]
21.5.5 TIME Less than a year after CRIME was published, security researchers Tal Be’ery and Amichai Shulman presented a new attack they called Timing Info-leak Made Easy (TIME) [17]. Conceptually, [...]
22.1 SMACK In 2015, a group of French security researchers with Benjamin Beurdouche systematically tested the then-popular open source TLS implementations for state-machine-related bugs and uncovered multiple critical security vulnerabilities [...]
22.2 FREAK FREAK stands for Factoring RSA Export Keys. The attack was discovered in 2017 ([27]) and can be seen as a variant of the cipher suite downgrade attack shown [...]
22.4 Heartbleed In 2014, Google’s security team member Neel Mehta privately reported an implementation bug to OpenSSL’s developer team. The same bug was independently discovered by security engineers working for [...]
22.6 Random number generation In Chapter 3 A Secret to Share, we learned that the security of most protocols and mechanisms depends on the generation of random sequences of bits [...]
22.8 Cloudbleed In 2017, Tavis Ormandy, a vulnerability researcher in Google’s Project Zero team, reported a security vulnerability in Cloudflare’s edge servers [76]. Cloudflare is a large Content Delivery Network [...]
22.8.1 Details of the the Cloudbleed bug To build a Ragel-based parser, the Ragel code is automatically transformed into C code. The C code is then compiled into an executable. [...]