Exit Zen
2
string ID 13
type: paragraph
English
A secure SSL/TLS connection requires a proper shutdown process to securely indicate the [@https://en.wikipedia.org/wiki/End-of-file ['EOF]] condition. This process prevents a type of attack known as a [@https://en.wikipedia.org/wiki/Transport_Layer_Security#Truncation_attack ['truncation attack]] in which an attacker can close the underlying transport layer and control the length of the last message in the SSL/TLS connection. A shutdown process consists of exchanging `close_notify` message between two parties. In __Asio__ these steps happen by calling `shutdown()` or `async_shutdown()` on `ssl::stream` object.
617/6170 · 617
3
string ID 25
type: section title
English
error::stream_truncated
23/230 · 23
4
string ID 27
type: paragraph
English
There are SSL/TLS implementations that don't perform a proper shutdown process and simply close the underlying transport layer instead. As a result, the EOF condition in these applications is not cryptographically secure and should not be relied upon. However, there are scenarios where an HTTPS client or server doesn't need EOF for determining the end of the last message:
374/3740 · 374
5
string ID 33
type: list
English
* The HTTP message has a `Content-Length` header, and the body is fully
71/710 · 71
6
string ID 36
type: list
English
* The HTTP message uses chunked transfer encoding, and the final chunk is
73/730 · 73
7
string ID 39
type: list
English
* The HTTP message doesn't contain a body, such as any response with a 1xx
74/740 · 74
8
string ID 42
type: paragraph
English
In such scenarios, `http::read` or `http::async_read` operations succeed as they don't need EOF to complete. However, the next operation on the stream would fail with an [@boost:/doc/html/boost_asio/reference/ssl__error__stream_errors.html `net::ssl::error::stream_truncated`] error.
283/2830 · 283
9
string ID 48
type: paragraph
English
For example, let's assume we are using Beast for communicating with an HTTPS server that doesn't perform a proper SSL/TLS shutdown:
131/1310 · 131
10
string ID 55
type: heading
English
Non-Compliant Peers and Unknown Body Length
43/430 · 43
11
string ID 57
type: paragraph
English
This is a rare case and indeed a security issue when HTTPS servers don't perform a proper SSL/TLS shutdown procedure and send an HTTP response message that relies on EOF to determine the end of the body. This is a security concern because without an SSL/TLS shutdown procedure, the EOF is not cryptographically secure, leaving the message body vulnerable to truncation attacks.
377/3770 · 377
12
string ID 63
type: paragraph
English
The following is an example that can read an HTTP response from such a server:
78/780 · 78
The translation has come to an end.