News for hackers. Stuff that matters.
Re:The Transport Layer Security (TLS) Protocol Version 1.3 by rocqua on Saturday August 11, 2018 @10:32AM (#17739809)
I only skimmed the RFC, but it seems like the SNI can be send either in the extensions in the client hello, or later in the encrypted extensions.
Re:The Transport Layer Security (TLS) Protocol Version 1.3 by rocqua on Saturday August 11, 2018 @11:22AM (#17739989)
Never mind, apparently encrypted extensions is only sent by the server to the client, not the other way around.
Re:The Transport Layer Security (TLS) Protocol Version 1.3 by nashvillecactus on Saturday August 11, 2018 @11:27AM (#17740015)
I think you got it right the first time, server_name is referring to SNI in this context: https://tools.ietf.org/html/rfc8446#page-37

Specifying which extensions are encrypted is part of the ClientHello. Encrypted Extensions are supposed to be sent directly after the client receives ServerHello.

With that said, I don't think we'll see implementations of encrypted SNI in the wild any time soon. From the ietf draft on encrypted SNI:

DISCLAIMER: This is very early a work-in-progress design and has not yet seen significant (or really any) security analysis. It should not be used as a basis for building production systems.

Re:The Transport Layer Security (TLS) Protocol Version 1.3 by rocqua on Saturday August 11, 2018 @11:36AM (#17740071)
That table is what I based my first post on. However, as far as I can find out, Encrypted Extensions are only ever send by the server to the client. [1]

The SNI that most people care about encrypting are those sent from the user to the server.

[1] https://tools.ietf.org/html/rfc8446#page-120

Re:The Transport Layer Security (TLS) Protocol Version 1.3 by nashvillecactus on Saturday August 11, 2018 @11:54AM (#17740151)
Okay, I see what you mean. Apparently I need to read more, because that completely flies in the face of how I thought this whole thing worked.