Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> The domain is there in the certificate itself.

With TLS 1.3, the certificate is in the encrypted portion of the handshake.



However as I understand the protocol the very first step of the TLS 1.3 handshake, the nonce generation, can be MiTMed sufficiently to allow an attacker to determine the target domain. It's only in the next step that server and client do authentication.

The attacker can't trivially continue the handshake beyond that point but that might give enough info to log the attempt and terminate the connection.


Or just connect up a second connection and see what certificate they send back.


That's nice to hear. I stand corrected, thank you.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: