diff options
| author | jsing <> | 2017-07-05 15:38:35 +0000 |
|---|---|---|
| committer | jsing <> | 2017-07-05 15:38:35 +0000 |
| commit | 610fb66a0a941297c7ccf07f3c6df668ebfcb4fc (patch) | |
| tree | 5f54f1faf70b7c6a24b039ec374662e43b876e23 /src/lib/libc | |
| parent | 1c100050d9aef1df290b0dfdc3e04e9f14fbc427 (diff) | |
| download | openbsd-610fb66a0a941297c7ccf07f3c6df668ebfcb4fc.tar.gz openbsd-610fb66a0a941297c7ccf07f3c6df668ebfcb4fc.tar.bz2 openbsd-610fb66a0a941297c7ccf07f3c6df668ebfcb4fc.zip | |
RFC 6066 states that IP literals are not permitted in "HostName" for a
TLS Server Name extension, however seemingly several clients (including
Python, Ruby and Safari) violate the RFC. Given that this is a fairly
widespread issue, if we receive a TLS Server Name extension that contains
an IP literal, pretend that we did not receive the extension rather than
causing a handshake failure.
Issue raised by jsg@
ok jsg@
Diffstat (limited to 'src/lib/libc')
0 files changed, 0 insertions, 0 deletions