1.18.0 libunbound DNS regression when built without OpenSSL #942
Comments
12 tasks
|
The issue is fixed with removal of the OpenSSL specific code for the nettle build. With that unbound-host works with a nettle libunbound only build. The bisect result and inspection are very nice! Thanks for the report, the fix is committed to the code repository. |
alyssais
added a commit
to alyssais/nixpkgs
that referenced
this issue
Sep 22, 2023
Link: NixOS#252325 (comment) Link: NLnetLabs/unbound#942 Fixes: 44500c3 ("unbound: 1.17.1 -> 1.18.0")
alyssais
added a commit
to alyssais/nixpkgs
that referenced
this issue
Sep 22, 2023
Link: NixOS#252325 (comment) Link: NLnetLabs/unbound#942 Fixes: 44500c3 ("unbound: 1.17.1 -> 1.18.0")
12 tasks
alyssais
added a commit
to NixOS/nixpkgs
that referenced
this issue
Sep 22, 2023
Link: #252325 (comment) Link: NLnetLabs/unbound#942 Fixes: 44500c3 ("unbound: 1.17.1 -> 1.18.0")
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
My Prosody XMPP server, which uses libunbound, can't do outgoing DNS since updating to 1.18.0.
To reproduce
Steps to reproduce the behavior:
Expected behavior
Prosody could make DNS requests, and send outgoing messages.
System:
unbound -Voutput: n/a; built with --with-libunbound-onlyAdditional information
Bisected to 7e6a7f3.
From inspection, it appears that, since
connect_sslctx_createreturns null if built without OpenSSL, setup will now always fail.The text was updated successfully, but these errors were encountered: