[Bug 208529] Error setting up SSL_CTX client key and cert and control-enable: no

[bugzilla...@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208529

Tilman Keskinoz <ar...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Product|Ports & Packages |Base System
Component|Individual Port(s) |conf
CC| |ar...@FreeBSD.org
Assignee|freebsd-ports-bugs@FreeBSD. |freebs...@FreeBSD.org
|org |
Version|Latest |10.3-RELEASE

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebs...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs...@freebsd.org"

[bugzilla...@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208529

Frans-Jan van Steenbeek <fran...@van-steenbeek.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |fran...@van-steenbeek.net

--- Comment #3 from Frans-Jan van Steenbeek <fran...@van-steenbeek.net> ---
Created attachment 170744
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=170744&action=edit
Suggested patch

See attached suggested patch.

Assuming people use unbound-control with local_unbound is a bit of a stretch,
especially since unbound-control-setup isn't even bundled. This patch tests the
functionality of the local resolver, which is just as good or even better than
querying the state. It assumes that local_unbound is configured to run on IPv4
localhost and that the .com zone is not somehow disabled or inaccessible. These
assumptions are *way* smaller than assuming unbound-control works. Besides
that, failure is less "messy" to look at.

[bugzilla...@freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208529

jonas...@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |jonas...@gmail.com

--- Comment #4 from jonas...@gmail.com ---
This is still an issue in 11.0-BETA3. It's very annoying having DNS broken by
default.