<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 09/02/2019 21:39, ѽ҉ᶬḳ℠ via
Unbound-users wrote:<br>
</div>
<blockquote type="cite"
cite="mid:71b09dcc-d6d6-537d-0e60-1b10d313766e@gmx.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
On 08/02/2019 19:21, ѽ҉ᶬḳ℠ via Unbound-users wrote:<br>
<blockquote type="cite"
cite="mid:cce5e72e-5d6d-f2d1-f6dd-c2fab56b64f1@gmx.net">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
With <br>
<br>
<blockquote type="cite">Fix <span class="hashtag">#4206:</span>
support openssl 1.0.2 for TLS hostname verification</blockquote>
<br>
I would have thought of this be gone but it is still present?<br>
<br>
<blockquote type="cite">unbound-checkconf error: no name
verification functionality in ssl library</blockquote>
<br>
<blockquote type="cite">Version 1.9.0<br>
linked libs: pluggable-event internal (it uses select),
OpenSSL 1.0.2q 20 Nov 2018<br>
linked modules: dns64 subnetcache respip validator iterator</blockquote>
<br>
</blockquote>
___<br>
<br>
Tests in the syntax of<br>
<br>
<blockquote type="cite">openssl s_client -servername foo.bar
-connect ip:443</blockquote>
<br>
returning <br>
<br>
<blockquote type="cite">Verify return code: 0 (ok)</blockquote>
<br>
Why then then the error in unbound 1.9.0?<br>
<br>
</blockquote>
<br>
After some digging
<a class="moz-txt-link-freetext" href="https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4206">https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4206</a><br>
</body>
</html>