summaryrefslogtreecommitdiffstats
path: root/lib/libssl/tls13_lib.c
diff options
context:
space:
mode:
authorflorian <florian@openbsd.org>2020-01-28 21:11:06 +0000
committerflorian <florian@openbsd.org>2020-01-28 21:11:06 +0000
commit23b78d59dd06c749764286c494b6da7648557f69 (patch)
treeee72b28a9a835b752cb1cdc529950b3187368aab /lib/libssl/tls13_lib.c
parentWith nc -NU netcat can probe if a UNIX stream socket is listening. (diff)
downloadwireguard-openbsd-23b78d59dd06c749764286c494b6da7648557f69.tar.xz
wireguard-openbsd-23b78d59dd06c749764286c494b6da7648557f69.zip
We are not correctly upgrading from "UNKNOWN" to "VALIDATING"
resulting in a "fatal in resolver: wrong unified cache set on resolver". I believe this happens because we are using an UNKNOWN resolving strategy to resolve queries. Disable the upgrade logic for now and always construct a fresh resolver context and set the unified context on it before any cache gets allocated. This causes a bit of memory churn on startup and when changing networks, but better than a crashing unwind. First observed by deraadt
Diffstat (limited to 'lib/libssl/tls13_lib.c')
0 files changed, 0 insertions, 0 deletions