policy.TLS_FORWARD: send SNI on wire if configured
- Feb 25, 2019
-
-
Petr Špaček authored
-
Petr Špaček authored
-
Petr Špaček authored
-
- Feb 22, 2019
-
-
It's mainly about the way we parse and validate them. Almost all of the parts of validation that were being done in modules/policy/policy.lua and daemon/tls.c got moved to daemon/bindings/net.c, so it's easier to follow that. Also more checks are being done now, e.g. contents of .pin_sha256 and .hostname strings.
-
In https world it's standard to do that, and it's relied on. Real-life example: 8.8.8.8#853 over TLSv1.3 won't send a certificate if we don't send SNI (no idea why; also they do send it with TLSv1.2). As a consequence, we no longer allow multiple hostnames per address-port tuple, but that didn't seem useful.
-