If a match is not found, the user may be warned of the discrepancy and the connection may abort as the mismatch may indicate an attempted man-in-the-middle attack. If a match occurs, the connection proceeds as normal. Once the server sends the certificate, the client examines it and compares the name it was trying to connect to with the name(s) included in the certificate. In more detail, when making a TLS connection, the client requests a digital certificate from the web server. Hence, if one server hosts multiple sites on a single listener, the server has no way to know which certificate to use in the TLS protocol. Prior to SNI, when making a TLS connection, the client had no way to specify which site it was trying to connect to. The SNI extension was specified in 2003 in RFC 3546. ![]() The desired hostname is not encrypted in the original SNI extension, so an eavesdropper can see which site is being requested. This also allows a proxy to forward client traffic to the right server during TLS/SSL handshake. It is the conceptual equivalent to HTTP/1.1 name-based virtual hosting, but for HTTPS. The extension allows a server to present one of multiple possible certificates on the same IP address and TCP port number and hence allows multiple secure ( HTTPS) websites (or any other service over TLS) to be served by the same IP address without requiring all those sites to use the same certificate. ![]() Server Name Indication ( SNI) is an extension to the Transport Layer Security (TLS) computer networking protocol by which a client indicates which hostname it is attempting to connect to at the start of the handshaking process. TLS extension for serve multiple HTTPS sites at the same IP address with different certificates
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |