From owner-freebsd-security@freebsd.org Fri Jun 3 18:34:27 2016 Return-Path: Delivered-To: freebsd-security@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 2D65AB691FA; Fri, 3 Jun 2016 18:34:27 +0000 (UTC) (envelope-from freebsd-security-local@be-well.ilk.org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 0D01D1DA3; Fri, 3 Jun 2016 18:34:26 +0000 (UTC) (envelope-from freebsd-security-local@be-well.ilk.org) Received: from lowell-desk.lan (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id D1C4D33C1E; Fri, 3 Jun 2016 14:34:19 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id 4873B39828; Fri, 3 Jun 2016 14:34:19 -0400 (EDT) From: Lowell Gilbert To: Slawa Olhovchenkov Cc: stable@freebsd.org, freebsd-security@freebsd.org Subject: Re: unbound and ntp issuse References: <20160602122727.GB75625@zxy.spb.ru> Date: Fri, 03 Jun 2016 14:34:18 -0400 In-Reply-To: <20160602122727.GB75625@zxy.spb.ru> (Slawa Olhovchenkov's message of "Thu, 2 Jun 2016 15:27:27 +0300") Message-ID: <44lh2mi0k5.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2016 18:34:27 -0000 Slawa Olhovchenkov writes: > Default install with local_unbound and ntpd can't be functional with > incorrect date/time in BIOS: > > Unbound requred correct time for DNSSEC check and refuseing queries > ("Jul 1 20:17:29 yellowrat unbound: [3444:0] info: failed to prime > trust anchor -- DNSKEY rrset is not secure . DNSKEY IN") > > ntpd don't have any numeric IP of ntp servers in ntp.conf -- only > symbolic names like 0.freebsd.pool.ntp.org, as result -- can't > resolve (see above, about DNSKEY). I can't see how this would happen. DNSSEC doesn't seem to be required in a regular install as far as I can see. Certainly I don't have any problem on any of my systems, and I've never configured an anchor on the internal systems. > IMHO, ntp.conf need to include some numeric IP of public ntp servers. Ouch; that's a terrible idea, for several different reasons.