Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #96, @AxbB36 pointed out that this library was sending IP addresses as server name extension values.
There's also another issue where this library was sending empty string values as server name extension values. I'm not sure that RFC 6066 Section 3 is identically as prescriptive about empty values, but the default go implementation does not send empty sni extensions:
https://github.com/golang/go/blob/36b81acfa19d9fedf6a0cd60c394fd7a7703834e/src/crypto/tls/handshake_client.go#L75
https://github.com/golang/go/blob/36b81acfa19d9fedf6a0cd60c394fd7a7703834e/src/crypto/tls/handshake_messages.go#L124-L135
You can see this empty server name extension value in the previous testdata recordings. Here's the client hello from
testdata/Client-TLSv12-UTLS-AES128-GCM-SHA256-Chrome-58
:Using
text2pcap
we can translate this into a pcap for analysis:The wireshark analysis of the tls client hello:
This PR uses the hostnameInSNI function to convert and validate names and then makes marshalling a
SNIExtension
with an invalid or emptye.ServerName
a no-op