From owner-freebsd-bugs@freebsd.org  Sat May 28 09:33:53 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9ED7AB4C84E
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 28 May 2016 09:33:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7E7E71432
 for <freebsd-bugs@FreeBSD.org>; Sat, 28 May 2016 09:33:53 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4S9Xpg1022187
 for <freebsd-bugs@FreeBSD.org>; Sat, 28 May 2016 09:33:53 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 208529] Error setting up SSL_CTX client key and cert and
 control-enable: no
Date: Sat, 28 May 2016 09:33:52 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: conf
X-Bugzilla-Version: 10.3-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: frans-jan@van-steenbeek.net
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-208529-8-6WG012l3jd@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-208529-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-208529-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 May 2016 09:33:53 -0000

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |frans-jan@van-steenbeek.net

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

See attached suggested patch.

Assuming people use unbound-control with local_unbound is a bit of a stretc=
h,
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 t=
han
querying the state. It assumes that local_unbound is configured to run on I=
Pv4
localhost and that the .com zone is not somehow disabled or inaccessible. T=
hese
assumptions are *way* smaller than assuming unbound-control works. Besides
that, failure is less "messy" to look at.

--=20
You are receiving this mail because:
You are the assignee for the bug.=