Исходное сообщение
"В Chrome добавлена экспериментальная поддержка протокола HTT..." Отправлено zanswer CCNA RS and S, 21-Сен-19 08:47
Что-то вроде такого: RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3 «2.2.  Resumption and Pre-Shared Key (PSK) Although TLS PSKs can be established out of band, PSKs can also be established in a previous connection and then used to establish a new connection ("session resumption" or "resuming" with a PSK). Once a handshake has completed, the server can send the client a PSK identity that corresponds to a unique key derived from the initial handshake (see Section 4.6.1). The client can then use that PSK identity in future handshakes to negotiate the use of the associated PSK. If the server accepts the PSK, then the security context of the new connection is cryptographically tied to the original connection and the key derived from the initial handshake is used to bootstrap the cryptographic state instead of a full handshake. In TLS 1.2 and below, this functionality was provided by "session IDs" and "session tickets" [RFC5077]. Both mechanisms are obsoleted in TLS 1.3. PSKs can be used with (EC)DHE key exchange in order to provide forward secrecy in combination with shared keys, or can be used alone, at the cost of losing forward secrecy for the application data.» Или вы имеете ввиду что-то другое?

Ваше сообщение
Имя*:
EMail:	Для отправки ответов на email укажите знак ! перед адресом, например, !user@host.ru (!! - не показывать email). Более тонкая настройка отправки ответов производится в профиле зарегистрированного участника форума.
Заголовок*:
Сообщение*:	> Что-то вроде такого: > RFC 8446 The Transport Layer Security (TLS) Protocol Version 1.3 > «2.2. Resumption and Pre-Shared Key (PSK) > Although TLS PSKs can be established out of band, PSKs can also > be established in a previous connection and then used to establish > a new connection ("session resumption" or "resuming" with a PSK). Once > a handshake has completed, the server can send the client a > PSK identity that corresponds to a unique key derived from the > initial handshake (see Section 4.6.1). The client can then use that > PSK identity in future handshakes to negotiate the use of the > associated PSK. If the server accepts the PSK, then the security > context of the new connection is cryptographically tied to the original > connection and the key derived from the initial handshake is used > to bootstrap the cryptographic state instead of a full handshake. In > TLS 1.2 and below, this functionality was provided by "session IDs" > and "session tickets" [RFC5077]. Both mechanisms are obsoleted in TLS 1.3. > PSKs can be used with (EC)DHE key exchange in order to provide > forward secrecy in combination with shared keys, or can be used > alone, at the cost of losing forward secrecy for the application > data.» > Или вы имеете ввиду что-то другое?
	Введите код, изображенный на картинке: